From d2ae5b39488b8e76e70d71a6881ee53caeefa2dc Mon Sep 17 00:00:00 2001 From: weishen Date: Sun, 26 Apr 2026 16:02:45 +0800 Subject: [PATCH] Auto-sync: 2026-04-26 16:02 --- wiki/concepts/Cloud-Computing.md | 52 + wiki/concepts/DevOps-Maturity-Model.md | 51 + wiki/concepts/Error-Budget.md | 142 ++- wiki/concepts/Immutable-Infrastructure.md | 147 ++- wiki/concepts/MVP.md | 49 + wiki/entities/DevOps-Maturity-Model.md | 121 +-- wiki/index.md | 978 +++++++++--------- wiki/log.md | 109 +- wiki/overview.md | 16 + .../sources/cloud-devop-maturity-guideline.md | 122 +-- ...del-a-detailed-guide-for-cloud-adoption.md | 147 +-- ...agile-practices-and-innovation-linkedin.md | 114 +- ...-from-traditional-it-to-advanced-devops.md | 252 ++--- ...ud-strategy-transform-your-business-roi.md | 223 ++-- ...e-vs-hybrid-cloud-differences-explained.md | 120 ++- ...ifferences-for-modern-disaster-recovery.md | 162 ++- ...ceptions-about-cloud-computing-linkedin.md | 133 ++- ...t-you-monitor-system-resources-in-style.md | 117 +-- ...t-i-know-about-cloud-service-delivery-1.md | 158 ++- ...ecops-best-practices-benefits-and-tools.md | 174 ++-- 20 files changed, 1656 insertions(+), 1731 deletions(-) create mode 100644 wiki/concepts/Cloud-Computing.md create mode 100644 wiki/concepts/DevOps-Maturity-Model.md create mode 100644 wiki/concepts/MVP.md diff --git a/wiki/concepts/Cloud-Computing.md b/wiki/concepts/Cloud-Computing.md new file mode 100644 index 00000000..af2158ab --- /dev/null +++ b/wiki/concepts/Cloud-Computing.md @@ -0,0 +1,52 @@ +--- +title: "Cloud Computing" +type: concept +tags: [cloud, infrastructure, iaas, paas, saas] +sources: [the-myths-and-misconceptions-about-cloud-computing-linkedin, what-i-know-about-cloud-service-delivery-1, cloud-maturity-model-a-detailed-guide-for-cloud-adoption] +last_updated: 2025-03-02 +--- + +## Definition + +Cloud computing is the delivery of computing services—including servers, storage, databases, networking, software, analytics, and intelligence—over the Internet ("the cloud") to offer faster innovation, flexible resources, and economies of scale. + +## Service Models + +- **IaaS (Infrastructure as a Service)**: Provides virtualized computing resources over the internet (e.g., AWS EC2, Azure VMs) +- **PaaS (Platform as a Service)**: Provides a platform for developing, running, and managing applications without dealing with infrastructure (e.g., AWS Elastic Beanstalk, Azure App Service) +- **SaaS (Software as a Service)**: Provides software applications over the internet on a subscription basis (e.g., Microsoft 365, Salesforce) + +## Key Characteristics + +- **On-demand self-service**: Provision resources as needed without human intervention +- **Broad network access**: Access services over the network via standard mechanisms +- **Resource pooling**: Multiple customers share infrastructure with logical separation +- **Rapid elasticity**: Scale resources up or down dynamically +- **Measured service**: Pay-as-you-go pricing model + +## Common Misconceptions + +According to [[the-myths-and-misconceptions-about-cloud-computing-linkedin]], the following misconceptions are prevalent: + +1. **Cloud is not secure** → Reality: Major providers invest heavily in security (encryption, MFA, ISO 27001, HIPAA, GDPR compliance) +2. **Cloud is just "someone else's computer"** → Reality: Cloud is a sophisticated network of data centers with redundancy and high availability +3. **Cloud is too expensive** → Reality: Pay-as-you-go model with proper management can be cost-effective +4. **You lose control of your data** → Reality: Cloud provides robust data governance and control tools +5. **Cloud is only for large enterprises** → Reality: SMBs can leverage enterprise-grade technology without large upfront investments +6. **Migration is too complex** → Reality: Phased migration and hybrid cloud solutions mitigate risks +7. **Cloud performance is unreliable** → Reality: SLAs often guarantee 99.99%+ uptime + +## Related Concepts + +- [[Hybrid-Cloud]]: Combining on-premises infrastructure with public cloud +- [[Multi-Cloud]]: Using multiple cloud providers simultaneously +- [[Cloud-Migration]]: The process of moving workloads to the cloud +- [[Cloud-Security]]: Security practices in cloud environments +- [[Pay-as-you-go]]: Cost model based on actual usage +- [[High-Availability]]: Design principle for minimizing downtime +- [[Serverless-Computing]]: Event-driven computing without server management + +## Aliases + +- Cloud +- 云计算 diff --git a/wiki/concepts/DevOps-Maturity-Model.md b/wiki/concepts/DevOps-Maturity-Model.md new file mode 100644 index 00000000..610ec471 --- /dev/null +++ b/wiki/concepts/DevOps-Maturity-Model.md @@ -0,0 +1,51 @@ +--- +title: "DevOps Maturity Model" +type: concept +tags: [DevOps, Maturity Assessment, CI/CD] +sources: [devops-maturity-model-from-traditional-it-to-advanced-devops] +last_updated: 2026-04-26 +--- + +## 定义 + +DevOps 成熟度模型（DevOps Maturity Model）是一种结构化框架，用于评估组织当前 DevOps 实践水平，识别改进领域，并规划向更高成熟度等级的演进路径。 + +该模型涵盖四个核心评估维度：**文化与战略**、**自动化**、**结构与流程**、**协作与共享**、**技术**，并通过五个递进阶段量化组织 DevOps 能力。 + +## 成熟度五阶段 + +| 阶段 | 名称 | 关键特征 | +|------|------|----------| +| Phase 1 | 初始/临时阶段 | 瀑布式开发，团队孤立，手动流程，反应式监控 | +| Phase 2 | 局部试点 | 小范围 DevOps 实践，版本控制引入，单元/集成测试 | +| Phase 3 | 自动化与定义 | 基础设施自动化，敏捷跨团队协作，安全扫描集成 | +| Phase 4 | 高度优化 | CI/CD 流水线，不可变基础设施，第三方依赖管理 | +| Phase 5 | 完全成熟 | 连续部署，零人工干预，数据驱动决策 | + +## 关键衡量指标 + +- **部署频率（Deployment Frequency）**：在设定周期内代码部署的频率 +- **变更前置时间（Lead Time）**：从代码提交到部署的时间 +- **变更失败率（Change Failure Rate）**：部署后引发故障或回滚的比例 +- **平均恢复时间（MTTR）**：从故障恢复到正常运行的时间 +- **错误预算（Error Budget）**：允许的生产环境错误和失败率 + +## 核心评估维度 + +1. **文化与战略**：团队协作、透明度、以客户为中心的产品思维 +2. **自动化**：CI/CD 流水线、基础设施即代码、测试自动化 +3. **结构与流程**：标准化流程、小批量工作、消除浪费 +4. **协作与共享**：开发与运维协同、知识共享、统一目标 +5. **技术选型**：工具链集成、监控告警、容器化解决方案 + +## 常见演进障碍 + +- 团队间沟通不畅 +- 缺乏清晰目标和策略 +- 抗拒变革 +- 投入不足 +- 治理薄弱 +- 流程僵化 + +## 来源 +- [[devops-maturity-model-from-traditional-it-to-advanced-devops]] diff --git a/wiki/concepts/Error-Budget.md b/wiki/concepts/Error-Budget.md index 4e70ba1d..bfb6c634 100644 --- a/wiki/concepts/Error-Budget.md +++ b/wiki/concepts/Error-Budget.md @@ -1,79 +1,63 @@ -# Error Budget - -## Definition -Error Budget is the permissible rate of errors and failures that a system can tolerate within a defined period without violating its reliability targets. It represents the "budget" of allowed failures before reliability SLAs are breached. - -Error Budget = 100% - (Actual Reliability Target) - -Example: If your target is 99.9% uptime, your error budget is 0.1% downtime per month. - -## Role in DevOps Maturity - -The DevOps Maturity Model explicitly lists Error Budget as one of the key metrics for measuring DevOps maturity. - -### Error Budget Across Maturity Levels -| Maturity | Error Budget Usage | -|----------|-------------------| -| Phase 1 | No error budget concept — reactive to failures as they occur | -| Phase 2 | Awareness growing — teams begin to understand the cost of failures | -| Phase 3 | Error budgets not explicitly managed — standardization helps but not measured | -| Phase 4 | Error budgets tracked — continuous monitoring enables measurement | -| Phase 5 | Error budgets actively used to drive deployment decisions — balancing innovation vs reliability | - -## How Error Budgets Work - -### The Concept -If your system achieves: -- **99.9% uptime**: 8.76 hours of downtime allowed per year (43.8 minutes per month) -- **99.99% uptime**: 52.6 minutes of downtime allowed per year (4.38 minutes per month) - -The "error budget" is the allowed bad events — once depleted, deployment velocity must slow down until reliability improves. - -### Error Budget Policy Example -- If error budget is >50% remaining: Deploy freely (encourage experimentation) -- If error budget is 25-50%: Proceed with caution, require additional testing -- If error budget is <25%: Pause non-critical deployments until budget recovers -- If error budget is exhausted: Stop all deployments, focus on reliability - -## Error Budget and SLOs - -| Concept | Role | -|---------|------| -| **SLO (Service Level Objective)** | The target reliability level (e.g., 99.9%) | -| **Error Budget** | The allowable failure budget derived from the SLO | -| **SLI (Service Level Indicator)** | The actual reliability measured | - -Error Budgets operationalize SLOs by creating concrete incentives for balancing innovation and reliability. - -## Business Impact - -### Benefits of Error Budget Thinking -1. **Incentivizes reliability**: Teams are motivated to maintain system health -2. **Enables calculated risk-taking**: Clear budget allows confident experimentation -3. **Prevents over-engineering**: Don't build for 99.999% when 99.9% is the target -4. **Aligns business and engineering**: Both understand the reliability-investment trade-off - -### Risks Without Error Budgets -- Over-investment in reliability beyond business needs -- Under-investment leading to frequent customer-facing failures -- Conflicting priorities between feature delivery and reliability -- No clear signal for when to slow down - -## Error Budget vs Change Failure Rate - -| Metric | Measures | -|--------|----------| -| **Error Budget** | Total allowable failures over a time period | -| **Change Failure Rate** | Percentage of deployments causing failures | - -These metrics work together: Low CFR preserves error budget; depleted error budget signals need to improve CFR. - -## Sources -- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] - -## Related Concepts -- [[concepts/SLO]] -- [[concepts/Change-Failure-Rate]] -- [[concepts/DORA-Metrics]] -- [[concepts/High-Availability]] -- [[concepts/DevOps-Maturity]] +--- +title: "Error Budget" +type: concept +tags: [SRE, Reliability, DevOps Metrics] +sources: [devops-maturity-model-from-traditional-it-to-advanced-devops] +last_updated: 2026-04-26 +--- + +## 定义 + +错误预算（Error Budget）是允许的、一定时间段内系统可以承受的错误和失败的数量或比例。它是一个平衡可靠性目标与创新速度的风险管理工具。 + +## 核心概念 + +错误预算源于 SRE（Site Reliability Engineering）理念，核心思想是： + +> 如果你的服务可靠性目标是 99.9%，那么你有 0.1% 的"错误预算"可以用于实验和发布。 + +## 计算方式 + +``` +Error Budget = (1 - Reliability SLO) × Time Period + +例如： +- 月 SLO = 99.9% +- 月错误预算 = 0.1% × 30天 × 24小时 = 0.72 小时（约 43 分钟） +``` + +## 在 DevOps 成熟度模型中的位置 + +在 DevOps 成熟度衡量指标体系中，错误预算是一个重要指标： + +> "Error Budget — The permissible rate of errors and failures in production." + +错误预算的使用策略因 DevOps 成熟度阶段不同而异： + +| 成熟度阶段 | 错误预算使用方式 | +|-----------|----------------| +| Phase 1-2 | 无正式错误预算概念 | +| Phase 3 | 开始建立 SLO，但未充分利用错误预算 | +| Phase 4 | 明确的错误预算政策，用于平衡创新与可靠性 | +| Phase 5 | 数据驱动决策，团队自主利用错误预算进行实验 | + +## 与相关概念的关系 + +- [[MTTR]]：错误预算与 MTTR 共同定义系统可靠性曲线 +- [[Change Failure Rate]]：高变更失败率会快速消耗错误预算 +- [[Deployment Frequency]]：高部署频率需要配合错误预算管理以维持可靠性目标 +- [[DevOps Maturity Model]]：错误预算是衡量组织成熟度的重要指标之一 + +## 错误预算政策示例 + +```yaml +SLO: 99.9%（每月 43 分钟错误预算） +策略: + - 错误预算充足（>50%）：可自由发布和实验 + - 错误预算中等（25-50%）：谨慎发布 + - 错误预算不足（<25%）：冻结发布，专注可靠性 + - 错误预算耗尽：停止所有非关键变更 +``` + +## 来源 +- [[devops-maturity-model-from-traditional-it-to-advanced-devops]] diff --git a/wiki/concepts/Immutable-Infrastructure.md b/wiki/concepts/Immutable-Infrastructure.md index be42cd04..652d996f 100644 --- a/wiki/concepts/Immutable-Infrastructure.md +++ b/wiki/concepts/Immutable-Infrastructure.md @@ -1,75 +1,72 @@ -# Immutable Infrastructure - -## Definition -Immutable Infrastructure is an approach where components are never modified after deployment. Instead of updating existing components, new versions are created and replaced entirely. - -## Concept -不可变基础设施是一种部署策略，其中服务器和基础设施组件一旦部署就不再修改。任何变更都需要创建新版本并替换整个组件。 - -## Core Principles - -### 1. Never Modify Running Systems -- 不直接在生产环境修改配置 -- 所有变更通过重新部署实现 -- 使用版本化配置和模板 - -### 2. Replace, Don't Modify -- 新版本 = 新环境 -- 旧版本直接销毁 -- 保证一致性 - -### 3. Infrastructure as Code -- 所有基础设施定义代码化 -- 版本控制所有配置 -- 可重复的部署流程 - -## Benefits for DevSecOps - -### Security Benefits -- **减少攻击面**：生产环境无交互式访问 -- **一致性保证**：每个环境完全相同 -- **快速回滚**：发现问题时快速切换 -- **审计简化**：代码即记录 - -### Operational Benefits -- 环境一致性 -- 可预测的部署 -- 简化的故障排除 -- 更容易扩展 - -## Implementation Patterns - -### Container-Based Approach -``` -容器镜像 = 应用 + 依赖 + 配置 -每次变更 → 新镜像版本 → 滚动更新 -``` - -### Cloud Infrastructure -- AWS：使用 AMI + Auto Scaling -- Kubernetes：使用 Pod 重建 -- Terraform：管理不可变配置 - -## Best Practices - -1. **使用标签（Tag）管理版本** -2. **自动化构建流程** -3. **保存历史镜像版本** -4. **实施蓝绿部署或滚动更新** -5. **监控不可变资源的变更** - -## Related Concepts -- [[DevSecOps]] — 不可变基础设施是安全架构的重要组成部分 -- [[Policy-as-Code]] — 策略代码化 -- [[Container-Lifecycle-Hardening]] — 容器安全加固 -- [[Blue-Green-Deployment]] — 蓝绿部署模式 -- [[Infrastructure-as-Code]] — 基础设施即代码 - -## Tools -- Packer — 镜像构建工具 -- Terraform — IaC 工具 -- Kubernetes — 容器编排 -- Docker — 容器化 - -## Sources -- [[what-is-devsecops-best-practices-benefits-and-tools]] +--- +title: "Immutable Infrastructure" +type: concept +tags: [Infrastructure as Code, DevOps, Cloud Native] +sources: [devops-maturity-model-from-traditional-it-to-advanced-devops] +last_updated: 2026-04-26 +--- + +## 定义 + +不可变基础设施（Immutable Infrastructure）是一种基础设施管理范式，服务器一旦部署就不再进行原地修改。当需要更新配置或修复问题时，整个服务器被替换为新版本，而不是在原有服务器上打补丁或更新。 + +## 核心原则 + +1. **不修改已部署的服务器**：任何变更都生成新服务器镜像 +2. **完整镜像部署**：使用预构建的镜像完整部署 +3. **自动化替换**：通过自动化流水线处理服务器生命周期 +4. **环境一致性**：所有环境使用相同的基础镜像 + +## 在 DevOps 成熟度模型中的位置 + +不可变基础设施是 **Phase 4（高度优化阶段）** 的关键特征： + +> "Immutable infrastructure replaces old servers rather than updating them." + +在该阶段，组织通过流水线管理基础设施和代码更新，不再依赖手动服务器修改。 + +## 不可变 vs 可变基础设施 + +| 维度 | 不可变基础设施 | 可变基础设施 | +|------|---------------|-------------| +| 更新方式 | 替换整个服务器 | 在原服务器上打补丁 | +| 一致性 | 所有环境高度一致 | 环境间可能存在差异 | +| 回滚难度 | 简单（切换回旧镜像） | 困难（需反向补丁） | +| 调试复杂度 | 低（快照确定） | 高（变化累积） | +| 部署速度 | 快（预构建镜像） | 慢（需逐步更新） | + +## 实现方式 + +### 容器化（推荐） +```dockerfile +# 每次构建生成新镜像 +FROM base-image:latest +RUN ./build.sh +# 部署时拉取新镜像，不修改原容器 +``` + +### 虚拟机镜像 +```bash +# Packer 创建镜像 +packer build template.json +# Terraform 用新 AMI 替换旧实例 +terraform apply +``` + +### 云基础设施 +```yaml +# Kubernetes 中使用 Immutable Pod +spec: + containers: + - image: myapp:v2.0 # 替换镜像而非修改容器 +``` + +## 与相关概念的关系 + +- [[Infrastructure as Code]]：不可变基础设施通常依赖 IaC 工具（Terraform、CloudFormation）实现 +- [[CI/CD Pipeline]]：不可变基础设施通过 CI/CD 流水线自动化构建和部署 +- [[DevOps Maturity Model]]：是 Phase 4 高度优化阶段的核心特征 +- [[Container-Lifecycle-Hardening]]：容器天然支持不可变范式，结合使用可提升安全性和一致性 + +## 来源 +- [[devops-maturity-model-from-traditional-it-to-advanced-devops]] diff --git a/wiki/concepts/MVP.md b/wiki/concepts/MVP.md new file mode 100644 index 00000000..2a0775d2 --- /dev/null +++ b/wiki/concepts/MVP.md @@ -0,0 +1,49 @@ +--- +title: "MVP" +type: concept +tags: [Product Development, Agile, Lean Startup] +sources: [devops-maturity-model-from-traditional-it-to-advanced-devops] +last_updated: 2026-04-26 +--- + +## 定义 + +MVP（Minimum Viable Product，最小可行产品）是指具有最小功能集的产品版本，仅包含核心功能足以满足早期用户需求并收集验证性反馈。 + +## 核心特征 + +- **最小功能集**：只实现解决核心问题所必需的最小功能 +- **快速验证**：尽早发布以获得真实用户反馈 +- **学习导向**：优先获取市场验证数据而非追求功能完备 +- **迭代演进**：基于反馈快速迭代改进 + +## 与 DevOps 成熟度的关系 + +在 DevOps 成熟度模型中，MVP 是 **Phase 4（高度优化阶段）** 的关键实践： + +> "Use of MVPs and management of tech debt to speed up releases." + +在该阶段，组织已建立成熟的 CI/CD 流水线，可以： +1. 快速构建和部署 MVP +2. 收集生产环境真实反馈 +3. 缩短从想法到验证的周期 +4. 降低大功能发布的风险 + +## MVP vs 完整产品 + +| 维度 | MVP | 完整产品 | +|------|-----|---------| +| 功能范围 | 最小核心功能 | 完整功能集 | +| 目标 | 验证假设 | 全面满足需求 | +| 发布时间 | 尽早发布 | 功能完备后发布 | +| 反馈来源 | 早期用户 | 广泛用户群 | +| 风险 | 低投入高学习 | 高投入风险大 | + +## 与相关概念的关系 + +- [[Agile]]：MVP 是敏捷开发的核心实践之一，支持快速迭代 +- [[Technical Debt]]：MVP 策略需要平衡快速交付与技术债务管理 +- [[DevOps Maturity Model]]：在 Phase 4 高度优化阶段，MVP 被用于加速发布周期 + +## 来源 +- [[devops-maturity-model-from-traditional-it-to-advanced-devops]] diff --git a/wiki/entities/DevOps-Maturity-Model.md b/wiki/entities/DevOps-Maturity-Model.md index 30bfe9d6..c35ac8c1 100644 --- a/wiki/entities/DevOps-Maturity-Model.md +++ b/wiki/entities/DevOps-Maturity-Model.md @@ -1,60 +1,61 @@ -# DevOps Maturity Model - -## Source -- [[sources/cloud-devop-maturity-guideline.md]] -- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] - -## Summary - -A framework for evaluating an organization's progress in adopting DevOps practices, typically ranging from ad-hoc processes to highly optimized and automated environments. The model defines **five maturity stages**: - -| Stage | Name | Key Characteristics | -|-------|------|---------------------| -| Phase 1 | Initial/Ad-Hoc | Siloed teams, waterfall approach, manual infrastructure, reactive monitoring, security only at release | -| Phase 2 | DevOps in Pockets | Small cross-functional teams, Agile introduction, version control, superficial automation, unit/integration testing | -| Phase 3 | Automated and Defined | Standardized processes, most infrastructure automated, security integrated into development process | -| Phase 4 | Highly Optimized | CI pipeline, immutable infrastructure, MVP and tech debt management, continuous security monitoring | -| Phase 5 | Fully Mature | Self-sufficient full-stack teams, multiple daily deployments, zero human intervention in pipeline | - -## Key Focus Areas - -1. **Culture and Strategy** — Teamwork, transparency, customer-centric mindset -2. **Automation** — AutoDevOps for continuous delivery and deployment -3. **Structure and Process** — Standardized, small-batch, transparent processes -4. **Collaboration and Sharing** — Cohesive teams leveraging diverse skill sets -5. **Technology** — Tool selection aligned with team needs - -## Quality Criteria - -- Assessment criteria (standards for evaluating maturity) -- Five maturity levels -- Core DevOps practices (release management, CI/CD, IaC, security) -- Relevant metrics (deployment frequency, MTTR, change failure rate) -- Cultural guides -- Tools and technologies -- Roles and responsibilities - -## Business Benefits - -- Quicker adjustment to market changes -- Capability to seize new opportunities -- Better scalability via IaC -- Enhanced operational performance -- Faster delivery times -- Improved quality via continuous monitoring and feedback - -## Security Integration (DevSecOps) - -The model emphasizes merging development, operations, and security into a unified process. Security progression: ad-hoc compliance scans → separate security team → security in design/architecture discussions → security updates in product workflow → preventing non-compliant code from production. - -## Related Concepts -- [[concepts/DevOps-Maturity]] -- [[concepts/DORA-Metrics]] -- [[concepts/DevSecOps]] -- [[concepts/CI-CD-Pipeline]] -- [[concepts/Infrastructure-as-Code]] -- [[concepts/Continuous-Deployment]] - -## Ingested -- Date: 2026-04-21 (initial) -- Date: 2026-04-24 (updated with Phase 1-5 details) +# DevOps Maturity Model + +## Source +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Summary + +A framework for evaluating an organization's progress in adopting DevOps practices, typically ranging from ad-hoc processes to highly optimized and automated environments. The model defines **five maturity stages**: + +| Stage | Name | Key Characteristics | +|-------|------|---------------------| +| Phase 1 | Initial/Ad-Hoc | Siloed teams, waterfall approach, manual infrastructure, reactive monitoring, security only at release | +| Phase 2 | DevOps in Pockets | Small cross-functional teams, Agile introduction, version control, superficial automation, unit/integration testing | +| Phase 3 | Automated and Defined | Standardized processes, most infrastructure automated, security integrated into development process | +| Phase 4 | Highly Optimized | CI pipeline, immutable infrastructure, MVP and tech debt management, continuous security monitoring | +| Phase 5 | Fully Mature | Self-sufficient full-stack teams, multiple daily deployments, zero human intervention in pipeline | + +## Key Focus Areas + +1. **Culture and Strategy** — Teamwork, transparency, customer-centric mindset +2. **Automation** — AutoDevOps for continuous delivery and deployment +3. **Structure and Process** — Standardized, small-batch, transparent processes +4. **Collaboration and Sharing** — Cohesive teams leveraging diverse skill sets +5. **Technology** — Tool selection aligned with team needs + +## Quality Criteria + +- Assessment criteria (standards for evaluating maturity) +- Five maturity levels +- Core DevOps practices (release management, CI/CD, IaC, security) +- Relevant metrics (deployment frequency, MTTR, change failure rate) +- Cultural guides +- Tools and technologies +- Roles and responsibilities + +## Business Benefits + +- Quicker adjustment to market changes +- Capability to seize new opportunities +- Better scalability via IaC +- Enhanced operational performance +- Faster delivery times +- Improved quality via continuous monitoring and feedback + +## Security Integration (DevSecOps) + +The model emphasizes merging development, operations, and security into a unified process. Security progression: ad-hoc compliance scans → separate security team → security in design/architecture discussions → security updates in product workflow → preventing non-compliant code from production. + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/DORA-Metrics]] +- [[concepts/DevSecOps]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/Continuous-Deployment]] + +## Ingested +- Date: 2026-04-21 (initial) +- Date: 2026-04-24 (updated with Phase 1-5 details) +- Date: 2026-04-26 (补充 DevOps 成熟度衡量指标、业务收益、安全集成的详细内容) diff --git a/wiki/index.md b/wiki/index.md index 1343a14f..abc1bf0e 100644 --- a/wiki/index.md +++ b/wiki/index.md @@ -4,494 +4,274 @@ - [Overview](overview.md) — living synthesis ## Sources -- [2026-04-26] [Autonomous Optimization Architect](sources/engineering-autonomous-optimization-architect.md) -- [2026-04-26] [Mobile App Builder Agent Personality](sources/engineering-mobile-app-builder.md) -- [2026-04-26] [Software Architect Agent Personality](sources/engineering-software-architect.md) -- [2026-04-26] [Godot Multiplayer Engineer Agent Personality](sources/godot-multiplayer-engineer.md) -- [2026-04-26] [Godot Shader Developer Agent Personality](sources/godot-shader-developer.md) -- [2026-04-26] [Godot Gameplay Scripter Agent Personality](sources/godot-gameplay-scripter.md) -- [2026-04-26] [Blender Add-on Engineer Agent Personality](sources/blender-addon-engineer.md) -- [2026-04-26] [Roblox Avatar Creator Agent Personality](sources/roblox-avatar-creator.md) -- [2026-04-26] [Roblox Systems Scripter Agent Personality](sources/roblox-systems-scripter.md) -- [2026-04-26] [Roblox Experience Designer](sources/roblox-experience-designer.md) -- [2026-04-26] [Unity Architect](sources/unity-architect.md) -- [2026-04-26] [Unity Multiplayer Engineer](sources/unity-multiplayer-engineer.md) -- [2026-04-26] [Unity Shader Graph Artist](sources/unity-shader-graph-artist.md) -- [2026-04-26] [Unity Editor Tool Developer](sources/unity-editor-tool-developer.md) -- [2026-04-26] [Unreal World Builder Agent Personality](sources/unreal-world-builder.md) -- [2026-04-26] [Unreal Systems Engineer](sources/unreal-systems-engineer.md) -- [2026-04-26] [Unreal Multiplayer Architect](sources/unreal-multiplayer-architect.md) -- [2026-04-26] [Unreal Technical Artist](sources/unreal-technical-artist.md) -- [2026-04-26] [Game Designer Agent Personality](sources/game-designer.md) -- [2026-04-25] [Narrative Designer Agent Personality](sources/narrative-designer.md) -- [2026-04-25] [Level Designer Agent Personality](sources/level-designer.md) -- [2026-04-25] [Technical Artist](sources/technical-artist.md) -- [2026-04-25] [Game Audio Engineer Agent](sources/game-audio-engineer.md) -- [2026-04-25] [AI Citation Strategist](sources/marketing-ai-citation-strategist.md) -- [2026-04-25] [Marketing Growth Hacker Agent](sources/marketing-growth-hacker.md) -- [2026-04-25] [Marketing Xiaohongshu Specialist](sources/marketing-xiaohongshu-specialist.md) -- [2026-04-25] [Marketing Podcast Strategist](sources/marketing-podcast-strategist.md) -- [2026-04-25] [Marketing Bilibili Content Strategist](sources/marketing-bilibili-content-strategist.md) -- [2026-04-25] [Marketing Content Creator](sources/marketing-content-creator.md) -- [2026-04-25] [Marketing Twitter Engager](sources/marketing-twitter-engager.md) -- [2026-04-25] [Marketing Livestream Commerce Coach](sources/marketing-livestream-commerce-coach.md) -- [2026-04-25] [Marketing TikTok Strategist](sources/marketing-tiktok-strategist.md) -- [2026-04-25] [Marketing SEO Specialist](sources/marketing-seo-specialist.md) -- [2026-04-25] [China Market Localization Strategist](sources/marketing-china-market-localization-strategist.md) -- [2026-04-25] [App Store Optimizer](sources/marketing-app-store-optimizer.md) -- [2026-04-25] [Marketing WeChat Official Account Manager](sources/marketing-wechat-official-account.md) -- [2026-04-25] [LinkedIn Content Creator](sources/marketing-linkedin-content-creator.md) -- [2026-04-25] [Marketing Weibo Strategist](sources/marketing-weibo-strategist.md) -- [2026-04-25] [Marketing Baidu SEO Specialist](sources/marketing-baidu-seo-specialist.md) -- [2026-04-25] [Marketing Carousel Growth Engine](sources/marketing-carousel-growth-engine.md) -- [2026-04-25] [Marketing Private Domain Operator](sources/marketing-private-domain-operator.md) -- [2026-04-25] [Marketing Short-Video Editing Coach](sources/marketing-short-video-editing-coach.md) -- [2026-04-25] [Social Media Strategist](sources/marketing-social-media-strategist.md) -- [2026-04-25] [Marketing Kuaishou Strategist](sources/marketing-kuaishou-strategist.md) -- [2026-04-25] [Marketing Video Optimization Specialist](sources/marketing-video-optimization-specialist.md) -- [2026-04-25] [Marketing Instagram Curator](sources/marketing-instagram-curator.md) -- [2026-04-25] [Marketing China E-Commerce Operator](sources/marketing-china-ecommerce-operator.md) -- [2026-04-25] [Marketing Reddit Community Builder](sources/marketing-reddit-community-builder.md) -- [2026-04-25] [Marketing Cross-Border E-Commerce Specialist](sources/marketing-cross-border-ecommerce.md) -- [2026-04-25] [Book Co-Author](sources/marketing-book-co-author.md) -- [2026-04-25] [Marketing Zhihu Strategist](sources/marketing-zhihu-strategist.md) -- [2026-04-25] [Marketing Douyin Strategist](sources/marketing-douyin-strategist.md) -- [2026-04-25] [Nexus Spatial: Full Agency Discovery Exercise](sources/nexus-spatial-discovery.md) -- [2026-04-25] [Multi-Agent Workflow: Startup MVP with Persistent Memory](sources/workflow-with-memory.md) -- [2026-04-25] [Multi-Agent Workflow: Landing Page Sprint](sources/workflow-landing-page.md) -- [2026-04-25] [Multi-Agent Workflow: Startup MVP](sources/workflow-startup-mvp.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Workflow Example: Book Chapter Development](sources/workflow-book-chapter.md) -- [2026-04-25] [Executive Summary Generator Agent Personality](sources/support-executive-summary-generator.md) -- [2026-04-25] [Finance Tracker Agent Personality](sources/support-finance-tracker.md) -- [2026-04-25] [Support Infrastructure Maintainer Agent Personality](sources/support-infrastructure-maintainer.md) -- [2026-04-25] [Support Responder Agent Personality](sources/support-support-responder.md) -- [2026-04-25] [Analytics Reporter Agent Personality](sources/support-analytics-reporter.md) -- [2026-04-25] [Support Legal Compliance Checker Agent Personality](sources/support-legal-compliance-checker.md) -- [2026-04-25] [Accessibility Auditor Agent Personality](sources/testing-accessibility-auditor.md) -- [2026-04-25] [Tool Evaluator Agent Personality](sources/testing-tool-evaluator.md) -- [2026-04-25] [Testing Evidence Collector Agent Personality](sources/testing-evidence-collector.md) -- [2026-04-25] [Test Results Analyzer Agent Personality](sources/testing-test-results-analyzer.md) -- [2026-04-25] [Performance Benchmarker Agent Personality](sources/testing-performance-benchmarker.md) -- [2026-04-25] [Testing Reality Checker](sources/testing-reality-checker.md) -- [2026-04-25] [Workflow Optimizer Agent Personality](sources/testing-workflow-optimizer.md) -- [2026-04-25] [API Tester Agent Personality](sources/testing-api-tester.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Backend Architect with Memory](sources/backend-architect-with-memory.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [2026-04-25] [Historian Agent Personality](sources/academic-historian.md) -- [2026-04-25] [Academic Geographer](sources/academic-geographer.md) -- [2026-04-25] [Academic Narratologist](sources/academic-narratologist.md) -- [2026-04-25] [Academic Anthropologist](sources/academic-anthropologist.md) -- [2026-04-25] [Academic Psychologist](sources/academic-psychologist.md) -- [2026-04-25] [Behavioral Nudge Engine](sources/product-behavioral-nudge-engine.md) -- [2026-04-25] [Product Sprint Prioritizer Agent](sources/product-sprint-prioritizer.md) -- [2026-04-25] [Product Trend Researcher Agent](sources/product-trend-researcher.md) -- [2026-04-25] [Product Manager Agent](sources/product-manager.md) -- [2026-04-25] [Product Feedback Synthesizer Agent](sources/product-feedback-synthesizer.md) -- [2026-04-25] [Specialized Developer Advocate](sources/specialized-developer-advocate.md) -- [2026-04-25] [Automation Governance Architect](sources/automation-governance-architect.md) -- [2026-04-25] [Report Distribution Agent](sources/report-distribution-agent.md) -- [2026-04-25] [Data Consolidation Agent](sources/data-consolidation-agent.md) -- [2026-04-25] [Supply Chain Strategist Agent](sources/supply-chain-strategist.md) -- [2026-04-25] [ZK Steward Agent](sources/zk-steward.md) -- [2026-04-25] [Korean Business Navigator](sources/specialized-korean-business-navigator.md) -- [2026-04-25] [French Consulting Market Navigator](sources/specialized-french-consulting-market.md) -- [2026-04-25] [Blockchain Security Auditor](sources/blockchain-security-auditor.md) -- [2026-04-25] [Sales Data Extraction Agent](sources/sales-data-extraction-agent.md) -- [2026-04-25] [Study Abroad Advisor](sources/study-abroad-advisor.md) -- [2026-04-25] [Agents Orchestrator](sources/agents-orchestrator.md) -- [2026-04-25] [MCP Builder Agent](sources/specialized-mcp-builder.md) -- [2026-04-25] [Compliance Auditor Agent](sources/compliance-auditor.md) -- [2026-04-25] [Specialized Salesforce Architect](sources/specialized-salesforce-architect.md) -- [2026-04-25] [LSP/Index Engineer Agent Personality](sources/lsp-index-engineer.md) -- [2026-04-25] [Model QA Specialist](sources/specialized-model-qa.md) -- [2026-04-25] [Corporate Training Designer](sources/corporate-training-designer.md) -- [2026-04-25] [Cultural Intelligence Strategist](sources/specialized-cultural-intelligence-strategist.md) -- [2026-04-25] [Healthcare Marketing Compliance Specialist](sources/healthcare-marketing-compliance.md) -- [2026-04-24] [Workflow Architect Agent Personality](sources/specialized-workflow-architect.md) -- [2026-04-24] [Government Digital Presales Consultant](sources/government-digital-presales-consultant.md) -- [2026-04-24] [Agentic Identity & Trust Architect](sources/agentic-identity-trust.md) -- [2026-04-24] [Document Generator Agent](sources/specialized-document-generator.md) -- [2026-04-24] [Identity Graph Operator](sources/identity-graph-operator.md) -- [2026-04-24] [Accounts Payable Agent Personality](sources/accounts-payable-agent.md) -- [2026-04-24] [Recruitment Specialist Agent](sources/recruitment-specialist.md) -- [2026-04-24] [Specialized Civil Engineer Agent](sources/specialized-civil-engineer.md) -- [2026-04-24] [Experiment Tracker Agent Personality](sources/project-management-experiment-tracker.md) -- [2026-04-24] [Studio Operations Agent Personality](sources/project-management-studio-operations.md) -- [2026-04-24] [Senior Project Manager Agent Personality](sources/project-manager-senior.md) -- [2026-04-24] [Jira Workflow Steward Agent Personality](sources/project-management-jira-workflow-steward.md) -- [2026-04-24] [Project Shepherd Agent Personality](sources/project-management-project-shepherd.md) -- [2026-04-24] [Studio Producer Agent Personality](sources/project-management-studio-producer.md) -- [2026-04-24] [visionOS Spatial Engineer](sources/visionos-spatial-engineer.md) -- [2026-04-24] [XR Interface Architect Agent Personality](sources/xr-interface-architect.md) -- [2026-04-24] [macOS Spatial/Metal Engineer Agent Personality](sources/macos-spatial-metal-engineer.md) -- [2026-04-24] [Terminal Integration Specialist](sources/terminal-integration-specialist.md) -- [2026-04-24] [XR Immersive Developer Agent Personality](sources/xr-immersive-developer.md) -- [2026-04-24] [XR Cockpit Interaction Specialist Agent](sources/xr-cockpit-interaction-specialist.md) -- [2026-04-24] [Sales Engineer Agent](sources/sales-engineer.md) -- [2026-04-24] [Pipeline Analyst Agent](sources/sales-pipeline-analyst.md) -- [2026-04-24] [Outbound Strategist Agent](sources/sales-outbound-strategist.md) -- [2026-04-24] [Deal Strategist Agent](sources/sales-deal-strategist.md) -- [2026-04-24] [Account Strategist Agent](sources/sales-account-strategist.md) -- [2026-04-24] [Sales Proposal Strategist](sources/sales-proposal-strategist.md) -- [2026-04-24] [Sales Coach Agent](sources/sales-coach.md) -- [2026-04-24] [Discovery Coach Agent](sources/sales-discovery-coach.md) -- [2026-04-24] [Paid Media Tracking & Measurement Specialist Agent](sources/paid-media-tracking-specialist.md) -- [2026-04-24] [Paid Media Ad Creative Strategist Agent](sources/paid-media-creative-strategist.md) -- [2026-04-24] [Paid Social Strategist](sources/paid-media-paid-social-strategist.md) -- [2026-04-24] [Paid Media Search Query Analyst Agent](sources/paid-media-search-query-analyst.md) -- [2026-04-24] [Paid Media Auditor Agent](sources/paid-media-auditor.md) -- [2026-04-24] [Paid Media PPC Campaign Strategist Agent](sources/paid-media-ppc-strategist.md) -- [2026-04-24] [Paid Media Programmatic & Display Buyer Agent](sources/paid-media-programmatic-buyer.md) -- [2026-04-24] [Visual Storyteller Agent](sources/design-visual-storyteller.md) -- [2026-04-24] [Inclusive Visuals Specialist](sources/design-inclusive-visuals-specialist.md) -- [2026-04-24] [Image Prompt Engineer Agent](sources/design-image-prompt-engineer.md) -- [2026-04-24] [UI Designer Agent Personality](sources/design-ui-designer.md) -- [2026-04-24] [Design Brand Guardian](sources/design-brand-guardian.md) -- [2026-04-24] [UX Researcher Agent Personality](sources/design-ux-researcher.md) -- [2026-04-24] [Design Whimsy Injector](sources/design-whimsy-injector.md) -- [2026-04-24] [ArchitectUX Agent Personality](sources/design-ux-architect.md) -- [2026-04-24] [Contributing to The Agency](sources/contributing.md) -- [2026-04-24] [为 The Agency 贡献代码](sources/contributing_zh-cn.md) -- [2026-04-24] [CTP Topic 12 Using SES SMTP service terraform module](sources/ctp-topic-12-using-ses-smtp-service-terraform-module.md) -- [2026-04-24] [Learning Sessions Cloud Transformation Programme-Deploying RDS via Terraform](sources/learning-sessions-cloud-transformation-programme-deploying-rds-via-terraform.md) -- [2026-04-24] [Learning Sessions Cloud Transformation Programme-20230808 183322-Meeting Recording](sources/learning-sessions-cloud-transformation-programme-20230808-183322-meeting-recordi.md) -- [2026-04-24] [CTP Topic 16 Cross-account Terraform modules](sources/ctp-topic-16-cross-account-terraform-modules.md) -- [2026-04-24] [Learning Sessions ECS Deployment using IAC - 20230808](sources/learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording.md) -- [2026-04-24] [CTP Topic 48 Terraform vs Terragrunt](sources/ctp-topic-48-terraform-vs-terragrunt.md) -- [2026-04-24] [Public Cloud Learning Sessions (OpenText) - AI Use Cases - 20241126 160106](sources/public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec.md) -- [2026-04-24] [Public Cloud Learning Sessions (OpenText) - Event Driven Architecture Part 2](sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091.md) -- [2026-04-24] [Public Cloud Learning Sessions (OpenText) - Generative AI & Prompt Engineering - 20241112](sources/public-cloud-learning-sessions-opentext-generative-ai-prompt-engineering-2024111.md) -- [2026-04-24] [Public Cloud Learning Sessions (OpenText) - Event Driven Architecture Part 1](sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091.md) -- [2026-04-24] [Public Cloud Learning Sessions - Serverless Computing - 20240903](sources/public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee.md) -- [2026-04-24] [Public Cloud Learning Sessions - Introduction to AI/ML with AWS](sources/public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin.md) -- [2026-04-24] [Cloud Learning Master Index](sources/cloud-learning-master-index.md) -- [2026-04-24] [CTP Topic 27 AWS Instance Scheduler](sources/ctp-topic-27-aws-instance-scheduler.md) -- [2026-04-24] [Public Cloud Learning Sessions - Budget Control - 20240319](sources/public-cloud-learning-sessions-budget-control-20240319-160204-meeting-recording.md) -- [2026-04-24] [CTP Topic 63 Optimise resource cost using automation](sources/ctp-topic-63-optimise-resource-cost-using-automation.md) -- [2026-04-24] [Public Cloud Learning Sessions - Storage Cost Optimization - 20240305](sources/public-cloud-learning-sessions-storage-cost-optimization-20240305-160037-meeting.md) -- [2026-04-24] [CTP Topic 71 PCG's guide to RightSizing, why, how when](sources/ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when.md) -- [2026-04-24] [Public Cloud Learning Sessions - Best practices for EC2 cost optimization in AWS - 20240529](sources/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md) -- [2026-04-24] [Public Cloud Learning Sessions - Reducing Cloud Costs - 20250318](sources/public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco.md) -- [2026-04-24] [CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs](sources/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md) -- [2026-04-24] [CTP Topic 15 Working with Renovatebot](sources/ctp-topic-15-working-with-renovatebot.md) -- [2026-04-24] [CTP Topic 56 Automated Infrastructure Testing](sources/ctp-topic-56-automated-infrastructure-testing.md) -- [2026-04-24] [Public Cloud Learning Sessions - Ollie Workflow and The Demand Process - 20240416](sources/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md) -- [2026-04-24] [CTP Topic 33 An Introduction to GitOps](sources/ctp-topic-33-an-introduction-to-gitops.md) -- [2026-04-24] [CTP Topic 3 Deploy and maintain infrastructure](sources/ctp-topic-3-deploy-and-maintain-infrastructure.md) -- [2026-04-24] [CTP Topic 9 CI CD with Gruntwork](sources/ctp-topic-9-ci-cd-with-gruntwork.md) -- [2026-04-24] [CTP Topic 32 Using Atlantis CICD for Infrastructure Deployments](sources/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md) -- [2026-04-24] [CTP Topic 2 Git](sources/ctp-topic-2-git.md) -- [2026-04-24] [CTP Topic 24 Micro Focus Product Privacy Framework](sources/ctp-topic-24-micro-focus-product-privacy-framework.md) -- [2026-04-24] [CTP Topic 49 Container Lifecycle Hardening Standards](sources/ctp-topic-49-container-lifecycle-hardening-standards.md) -- [2026-04-24] [CTP Topic 21 Supply Chain Security in Micro Focus](sources/ctp-topic-21-supply-chain-security-in-micro-focus.md) -- [2026-04-24] [CTP Topic 52 3 Lines of Defence (3LoD) framework Cloud Security Posture Management (CSPM)](sources/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md) -- [2026-04-24] [CTP Topic 55 AWS Firewall Manager](sources/ctp-topic-55-aws-firewall-manager.md) -- [2026-04-24] [CTP Topic 37 Secrets Certificates Management](sources/ctp-topic-37-secrets-certificates-management.md) -- [2026-04-24] [CTP Topic 62 AWS Secrets Manager](sources/ctp-topic-62-aws-secrets-manager.md) -- [2026-04-24] [Public Cloud Learning Sessions - OpenText GIS Security Policies - 20241015](sources/public-cloud-learning-sessions-opentext-gis-security-policies-20241015-160257-me.md) -- [2026-04-24] [CTP Topic 64 Scaling out with Amazon EKS](sources/ctp-topic-64-scaling-out-with-amazon-eks.md) -- [2026-04-24] [CTP Topic 67 Cloud native observability using OpenTelemetry](sources/ctp-topic-67-cloud-native-observability-using-opentelemetry.md) -- [2026-04-24] [Public Cloud Learning Sessions - EKS Optimization Part 2 of 3 - Running Containers with Bottlerocket OS](sources/public-cloud-learning-sessions-eks-optimization-part-2-of-3-running-containers-w.md) -- [2026-04-24] [CTP Topic 42 Grafana Observability Dashboard](sources/ctp-topic-42-grafana-observability-dashboard.md) -- [2026-04-24] [Public Cloud Learning Sessions - Observability with OpenTelemetry - 20240402](sources/public-cloud-learning-sessions-observability-with-opentelemetry-20240402-160113.md) -- [2026-04-24] [CTP Topic 54 ESM SaaS Log Analytics](sources/ctp-topic-54-esm-saas-log-analytics.md) -- [2026-04-24] [CTP Topic 59 Achieving reliability with Amazon EKS](sources/ctp-topic-59-achieving-reliability-with-amazon-eks.md) -- [2026-04-24] [CTP Topic 29 Cloud Monitoring – SaaS LZ accounts](sources/ctp-topic-29-cloud-monitoring-saas-lz-accounts.md) -- [2026-04-24] [CTP Topic 39 Implementing EKS in the AWS Lab Landing Zone](sources/ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone.md) -- [2026-04-24] [Public Cloud Learning Sessions - EKS Optimization Part 1 of 3 - Compute Optimization with Karpenter](sources/public-cloud-learning-sessions-eks-optimization-part-1-of-3-compute-optimization.md) -- [2026-04-24] [CTP Topic 70 EKS deployment using IAC](sources/ctp-topic-70-eks-deployment-using-iac.md) -- [2026-04-24] [CTP Topic 60 - Monitor AWS using Hyperscale Observability with Grafana](sources/ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana.md) -- [2026-04-24] [Public Cloud Learning Sessions - EKS Optimization Part 3 of 3 - Introduction to EKS Auto Mode](sources/public-cloud-learning-sessions-eks-optimization-part-3-of-3-introduction-to-eks.md) -- [2026-04-24] [CTP Topic 8 - Implementation of Cloud Monitoring using Micro Focus Operations Bridge Manager](sources/ctp-topic-8-implementation-of-cloud-monitoring-using-micro-focus-operations-brid.md) -- [2026-04-23] [CTP Topic 11 AD Integration and Login using AD Accounts](sources/ctp-topic-11-ad-integration-and-login-using-ad-accounts.md) -- [2026-04-23] [CTP Topic 5 - AWS Identity and Access Management (IAM)](sources/ctp-topic-5-aws-identity-and-access-management-iam.md) -- [2026-04-23] [Learning Sessions Identity Governance VSM Replacement - 20231128](sources/learning-sessions-identity-governance-vsm-replacement-20231128-160326-meeting-re.md) -- [2026-04-23] [Public Cloud Learning Sessions - AWS End User Compute Services - 20240430](sources/public-cloud-learning-sessions-aws-end-user-compute-services-20240430-160120-mee.md) -- [2026-04-23] [Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109](sources/public-cloud-learning-sessions-applicable-business-analysis-techniques-20240109.md) -- [2026-04-23] [Public Cloud Learning Sessions (OpenText) - Product Hub (PHT) Overview and Q&A - 20240806](sources/public-cloud-learning-sessions-opentext-product-hub-pht-overview-and-qa-20240806.md) -- [2026-04-23] [Public Cloud Learning Sessions - Tagging Standards for All Hyperscalers - 20240123](sources/public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123-1.md) -- [2026-04-23] [CTP Topic 23 Introduction to the Technical Architecture Team and Function](sources/ctp-topic-23-introduction-to-the-technical-architecture-team-and-function.md) -- [2026-04-23] [CTP Topic 57 Product backlog managing demand](sources/ctp-topic-57-product-backlog-managing-demand.md) -- [2026-04-23] [Public Cloud Learning Sessions (OpenText) - Thor Platform & Flows](sources/public-cloud-learning-sessions-opentext-thor-platform-flows-20241210-160056-meet.md) -- [2026-04-23] [CTP Topic 6 AWS Workspaces Demo](sources/ctp-topic-6-aws-workspaces-demo.md) -- [2026-04-23] [CTP Topic 53 Why bother with Cloud](sources/ctp-topic-53-why-bother-with-cloud.md) -- [2026-04-23] [Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab Migration](sources/public-cloud-learning-sessions-opentext-github-enterprise-to-gitlab-migration-20.md) -- [2026-04-23] [Public Cloud Learning Sessions - OpenText Tagging Standard v2 - 20250429](sources/public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meet.md) -- [2026-04-23] [CTP Topic 41 NFR's and Error Budgets](sources/ctp-topic-41-nfrs-and-error-budgets.md) -- [2026-04-23] [CTP Topic 10 AWS Landing Zone (LZ) Data Collection, Tagging Related Security](sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md) -- [2026-04-23] [CTP Topic 20 Program demand process flow and PoC onboarding](sources/ctp-topic-20-program-demand-process-flow-and-poc-onboarding.md) -- [2026-04-23] [CTP Topic 4 Using Agile to Run the Cloud Transformation Programme](sources/ctp-topic-4-using-agile-to-run-the-cloud-transformation-program.md) -- [2026-04-23] [CTP Topic 65 Tracing the Value Delivered in Cloud Transformation](sources/ctp-topic-65-tracing-the-value-delivered-in-cloud-transformation.md) -- [2026-04-23] [Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723](sources/public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2.md) -- [2026-04-23] [CTP Topic 30 Managing Change](sources/ctp-topic-30-managing-change.md) -- [2026-04-23] [CTP Topic 69 Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on AWS](sources/ctp-topic-69-best-practices-for-migrating-on-premises-iod-virtual-machines-to-vm.md) -- [2026-04-23] [CTP Topic 31 Network Segregation and Secure Access to the New AWS Landing Zones](sources/ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones.md) -- [2026-04-23] [CTP Topic 18 Wide Area Networking in AWS Cloud](sources/ctp-topic-18-wide-area-networking-in-aws-cloud.md) -- [2026-04-23] [CTP Topic 43 VMware Cloud on AWS](sources/ctp-topic-43-vmware-cloud-on-aws.md) -- [2026-04-23] [CTP Topic 61 Workload VPC provision with IPAM Automation](sources/ctp-topic-61-workload-vpc-provision-with-ipam-automation.md) -- [2026-04-23] [CTP Topic 45 Automatic IP address allocation with IPAM](sources/ctp-topic-45-automatic-ip-address-allocation-with-ipam.md) -- [2026-04-23] [CTP Topic 19 Configuring DNS within AWS LZs](sources/ctp-topic-19-configuring-dns-within-aws-lzs.md) -- [2026-04-23] [CTP Topic 36 SendGrid as an Email Service](sources/ctp-topic-36-sendgrid-as-an-email-service.md) -- [2026-04-23] [CTP Topic 22 Global DNS service offerings](sources/ctp-topic-22-global-dns-service-offerings.md) -- [2026-04-23] [CTP Topic 50 AMI Roadmap for AWS AMIs](sources/ctp-topic-50-ami-roadmap-for-aws-amis.md) -- [2026-04-23] [CTP Topic 40 SaaS Database Architecture On AWS Cloud](sources/ctp-topic-40-saas-database-architecture-on-aws-cloud.md) -- [2026-04-23] [CTP Topic 26 Standard AMI – build, publish, share processes](sources/ctp-topic-26-standard-ami-build-publish-share-processes.md) -- [2026-04-23] [CTP Topic 68 Introduction to Redshift](sources/ctp-topic-68-introduction-to-redshift.md) -- [2026-04-23] [CTP Topic 58 AWS EC2 Image Builder](sources/ctp-topic-58-aws-ec2-image-builder.md) -- [2026-04-23] [CTP Topic 25 Labs Landing Zone Overview - ITOM Teams](sources/ctp-topic-25-labs-landing-zone-overview-itom-teams.md) -- [2026-04-23] [Learning Sessions: Standard AMI Updates 20231205](sources/learning-sessions-standard-amis-updates-20231205-160324-meeting-recording-2.md) -- [2026-04-23] [CTP Topic 7 SaaS Landing Zone Design](sources/ctp-topic-7-saas-landing-zone-design.md) -- [2026-04-23] [CTP Topic 34 Azure Landing Zone Architecture Overview](sources/ctp-topic-34-azure-landing-zone-architecture-overview.md) -- [2026-04-23] [CTP Topic 35 AWS Landing Zone Design Refresher (SaaS Labs)](sources/ctp-topic-35-aws-landing-zone-design-refresher-saas-labs.md) -- [2026-04-23] [CTP Topic 10 AWS Landing Zone (LZ) Data Collection, Tagging Related Security](sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md) -- [2026-04-23] [CTP Topic 73 AWS Backup Implementation of the Cloud Transformation Programme](sources/ctp-topic-73-aws-backup-implementation-of-the-cloud-transformation-program.md) -- [2026-04-23] [CTP Topic 28 AWS Tag Validation Tool](sources/ctp-topic-28-aws-tag-validation-tool.md) -- [2026-04-23] [CTP Topic 47 Enterprise Architecture Cloud Standards](sources/ctp-topic-47-enterprise-architecture-cloud-standards.md) -- [2026-04-23] [CTP Topic 72 Implementing an Enterprise DR Strategy Using AWS Backup](sources/ctp-topic-72-implementing-an-enterprise-dr-strategy-using-aws-backup.md) -- [2026-04-23] [CTP Topic 1 Gruntwork Landing Zone Architecture](sources/ctp-topic-1-gruntwork-landing-zone-architecture.md) -- [2026-04-23] [CTP Topic 51 Architecting with AWS Purpose-Built Databases](sources/ctp-topic-51-architecting-with-aws-purpose-built-databases.md) -- [2026-04-23] [CTP Topic 46 NetApps on AWS](sources/ctp-topic-46-netapps-on-aws.md) -- [2026-04-23] [CTP Topic 17 Active Directory Services in Gruntwork AWS LZs](sources/ctp-topic-17-active-directory-services-in-gruntwork-aws-lzs.md) -- [2026-04-23] [CTP Topic 66 Exposing the differences between PostgreSQL RDS and Aurora](sources/ctp-topic-66-exposing-the-differences-between-postgresql-rds-and-aurora.md) -- [2026-04-23] [CTP Topic 14 Octane Hub on AWS Real Life Experience Moving Production Services](sources/ctp-topic-14-octane-hub-on-aws-real-life-experience-moving-production-services-i.md) -- [2026-04-23] [CTP Topic 44 AWS Backup in Micro Focus](sources/ctp-topic-44-aws-backup-in-micro-focus.md) -- [2026-04-23] [Blogwatcher Daily 技能收藏](sources/blogwatcher-daily收藏.md) -- [2026-04-23] [实战笔记：本地部署 RSSHub 并获取 YouTube 订阅](sources/实战笔记-本地部署-rsshub-并获取-youtube-订阅.md) -- [2026-04-23] [Mac必装软件清单](sources/mac必装软件清单-2026-04-17.md) -- [2026-04-23] [Install WSL](sources/install-wsl.md) -- [2026-04-23] [WSL2 启动与网络配置指南](sources/wsl2-启动与网络配置指南.md) -- [2026-04-23] [fireworks-tech-graph](sources/fireworks-tech-graph.md) -- [2026-04-23] [Obsidian 官方 CLI 命令全景速查表](sources/obsidian-官方-cli-命令全景速查表.md) -- [2026-04-23] [Obsidian CLI](sources/obsidian-cli.md) -- [2026-04-23] [我做了个 Skill：让 AI 帮你生成 Logo 和图标](sources/我做了个-skill-让-ai-帮你生成-logo-和图标.md) -- [2026-04-23] [Obsidian 必装 Skills](sources/obsidian-必装-skills.md) -- [2026-04-23] [在 Ubuntu 安装 Ollama 并运行 Qwen2.5‑Coder 7B](sources/在-ubuntu-安装-ollama-并运行-qwen2-5‑coder-7b.md) -- [2026-04-23] [Learn AI for free directly from top companies](sources/learn-ai-for-free-directly-from-top-companies.md) -- [2026-04-23] [I Went Through Every AI Memory Tool I Could Find. There Are Two Camps.](sources/ai-memory-tools-two-camps.md) -- [2026-04-23] [可自动化、可扩展、AI增强的电商数据采集与处理系统](sources/可自动化-可扩展-ai增强的电商数据采集与处理系统.md) -- [2026-04-23] [Building your Quartz](sources/building-your-quartz.md) -- [2026-04-23] [电商如何选品 - 如何找到爆款选品策略](sources/电商如何选品-如何找到爆款-选品策略.md) -- [2026-04-23] [电商视频Prompt库](sources/电商视频prompt.md) -- [2026-04-23] [TikTok Shop - Apache Superset Dashboard设计思路](sources/tiktok-shop-apache-superset-dashboard设计思路.md) -- [2026-04-23] [做TK跨境思路不对努力白费](sources/做tk跨境思路不对努力白费.md) -- [2026-04-23] [超达物流定价](sources/超达物流定价.md) -- [2026-04-23] [TK美国面单授权及操作流程](sources/tk美国面单授权及操作流程.md) -- [2026-04-23] [Scrapy + Playwright 抓取TikTok Shop Data](sources/scrapy-playwright-抓取tiktok-shop-data.md) -- [2026-04-23] [GOG CLI 安装配置指南](sources/gog-cli-安装配置指南.md) -- [2026-04-23] [Last30Days 使用指南](sources/last30days-使用指南.md) -- [2026-04-23] [如何利用Sora接口实现视频自动化生成工作流](sources/如何利用sora接口实现视频自动化生成工作流.md) -- [2026-04-23] [If You Have Multiple Interests, Do Not Waste the Next 2-3 Years](sources/if-you-have-multiple-interests-do-not-waste-the-next-2-3-years-如果你有多项兴趣爱好-不要浪费接下来的两三年时间.md) -- [2026-04-23] [我用 Gemini 3 一口气做了 10 个应用，附教程](sources/我用-gemini-3-一口气做了-10-个应用-附教程.md) -- [2026-04-23] [Multi-Agent System Reliability](sources/multi-agent-system-reliability.md) -- [2026-04-23] [全网最全！Nano Banana 2 使用指南（2025年12月更新）](sources/全网最全-nano-banana-2-使用指南-2025年12月更新-1.md) -- [2026-04-23] [2025 年 11 个神级 AI 开源平替，GitHub 杀疯了](sources/2025-年-11-个神级-ai-开源平替-github-杀疯了.md) -- [2026-04-23] [AI 解决方案专家培训课程](sources/ai-解决方案专家培训课程.md) -- [2026-04-23] [RAG从入门到精通系列1：基础RAG](sources/rag从入门到精通系列1-基础rag.md) -- [2026-04-23] [固定镜头短视频制作的AI全流程解析](sources/固定镜头短视频制作的ai全流程解析.md) -- [2026-04-23] [大模型相关术语和框架总结｜LLM、MCP、Prompt、RAG、vLLM、Token、数据蒸馏](sources/大模型相关术语和框架总结｜llm-mcp-prompt-rag-vllm-token-数据蒸馏.md) -- [2026-04-23] [Nano Banana Pro 提示词指南与策略（上篇）](sources/nano-banana-pro-prompting-guide-strategies-1.md) -- [2026-04-23] [我的工具集](sources/我的工具集.md) -- [2026-04-23] [3.2 万人收藏的 Claude Skills，才是 AI 这条路上最值得研究的一套范式！](sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式.md) -- [2026-04-23] [如何写出完美的Prompt（提示词）？](sources/如何写出完美的prompt-提示词.md) -- [2026-04-23] [codecrafters-io/build-your-own-x: Master programming by recreating your favorite technologies from scratch](sources/codecrafters-iobuild-your-own-x-master-programming-by-recreating-your-favorite-technologies-from-scratch.md) -- [2026-04-23] [系统提示词构建原则](sources/系统提示词构建原则.md) -- [2026-04-23] [GitHub 上 5000 人收藏的 Vibe Coding 神级指南](sources/github-上-5000-人收藏的-vibe-coding-神级指南.md) -- [2026-04-23] [How to Get the RSS Feed For Any YouTube Channel](sources/how-to-get-the-rss-feed-for-any-youtube-channel.md) -- [2026-04-23] [3.2 万人收藏的 Claude Skills，才是 AI 这条路上最值得研究的一套范式！](sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式-1.md) -- [2026-04-22] [不会Gemini的产品经理真的要被淘汰了 | 附保姆级PRD生成指南](sources/不会gemini的产品经理真的要被淘汰了-附保姆级prd生成指南.md) -- [2026-04-22] [7 ways I use NotebookLM to make my life easier](sources/7-ways-i-use-notebooklm-to-make-my-life-easier.md) -- [2026-04-22] [Never write another prompt](sources/never-write-another-prompt.md) -- [2026-04-22] [一语点醒梦中人](sources/一语点醒梦中人.md) -- [2026-04-22] [Best 7 news API data feeds - AI News](sources/best-7-news-api-data-feeds-ai-news.md) -- [2026-04-22] [Claude Prompt Library 汇总表](sources/useful-prompt-lib.md) -- [2026-04-22] [二创视频必不可少！2025年最热门AI工具推荐合集-AI配音、声音克隆](sources/二创视频必不可少-2025年最热门ai工具推荐合集-ai配音-声音克隆.md) -- [2026-04-22] [The Picture They Paint of You](sources/the-picture-they-paint-of-you.md) -- [2026-04-22] [Nano Banana 提示词框架](sources/nano-banana-提示词框架.md) -- [2026-04-22] [谷歌深夜甩出一份【Nano Banana Pro提示词指南】，手把手教你生产专业级内容，实战案例+提示词模版](sources/谷歌深夜甩出一份-nano-banana-pro提示词指南-手把手教你生产专业级内容-实战案例-提示词模版.md) -- [2026-04-22] [详细！离线部署大模型：ollama+deepseek+open-webui安装使用方法及常见问题解决 1](sources/详细-离线部署大模型-ollama-deepseek-open-webui安装使用方法及常见问题解决-1.md) -- [2026-04-22] [OpenAI ChatGPT 个性化定义](sources/openai-chatgpt-个性化定义.md) -- [2026-04-22] [清华出的DeepSeek使用手册，104页，真的是太厉害了！（免费领取）](sources/清华出的deepseek使用手册-104页-真的是太厉害了-免费领取.md) -- [2026-04-22] [LLMs、RAG、AI Agent 三个到底什么区别？](sources/llms-rag-ai-agent-三个到底什么区别.md) -- [2026-04-22] [A Formalization of Recursive Self-Optimizing Generative Systems](sources/a-formalization-of-recursive-self-optimizing-generative-systems.md) -- [2026-04-22] [文字生成视频网站推荐](sources/文字生成视频网站推荐.md) -- [2026-04-22] [Google 神级生产力工具，所有 GitHub 开源平替都找到了。](sources/google-神级生产力工具-所有-github-开源平替都找到了.md) -- [2026-04-22] [教學 ChatGPT 先做知識整理，再讓 Canva、 Gamma AI 輸出簡報](sources/教學-chatgpt-先做知識整理-再讓-canva-gamma-ai-輸出簡報.md) -- [2026-04-22] [Designing for Agentic AI](sources/designing-for-agentic-ai.md) -- [2026-04-22] [14个免费的AI图生视频工具，用AI让图片动起来](sources/14个免费的ai图生视频工具-用ai让图片动起来-ai视频教程-ai自动化工作流定制服务-ai培训学习平台-黑喵大叔.md) -- [2026-04-22] [养虾日记5：深夜与苏轼聊AI，他说：被浪打下去还能爬起来的才叫风流](sources/养虾日记5-深夜与苏轼聊ai-他说-被浪打下去还能爬起来的才叫风流.md) -- [2026-04-22] [养虾日记4：一次「Context Limit Exceeded」错误排查：我以为是小问题，结果踩了大坑](sources/养虾日记4-一次「context-limit-exceeded」错误排查-我以为是小问题-结果踩了大坑.md) -- [2026-04-22] [不谈技术：普通人该怎么在AI时代赚钱？](sources/不谈技术-普通人该怎么在ai时代赚钱.md) -- [2026-04-22] [养虾日记3：用 Obsidian + Gitea 为 AI 助手构建持久化笔记系统](sources/养虾日记3-用-obsidian-gitea-为-ai-助手构建持久化笔记系统.md) -- [2026-04-22] [养龙虾5天血泪史：我的AI Agent为什么总失忆？OpenClaw 记忆调试全记录](sources/养龙虾5天血泪史-我的ai-agent为什么总失忆-openclaw-记忆调试全记录.md) -- [2026-04-22] [养虾日记1：我用 OpenClaw 管了 28 万张照片：一次真实的多设备照片整理实战](sources/养虾日记1-我用-openclaw-管了-28-万张照片-一次真实的多设备照片整理实战.md) -- [2026-04-22] [养虾日记2：让Agent更懂你：OpenClaw + Self-Improving 复盘实战案例分享](sources/养虾日记2-让agent更懂你-openclaw-self-improving-复盘实战案例分享.md) -- [2026-04-22] [X Account Analysis](sources/x-account-analysis.md) -- [2026-04-22] [Phone Call Notifications](sources/phone-call-notifications.md) -- [2026-04-22] [Autonomous Educational Game Development Pipeline](sources/autonomous-game-dev-pipeline.md) -- [2026-04-22] [arXiv Paper Reader](sources/arxiv-paper-reader.md) -- [2026-04-22] [Semantic Memory Search](sources/semantic-memory-search.md) -- [2026-04-22] [OpenClaw as Desktop Cowork (AionUi) — Remote Rescue & Multi-Agent Hub](sources/aionui-cowork-desktop.md) -- [2026-04-22] [Family Calendar Aggregation & Household Assistant](sources/family-calendar-household-assistant.md) -- [2026-04-22] [Multi-Source Tech News Digest](sources/multi-source-tech-news-digest.md) -- [2026-04-22] [X/Twitter Automation from Chat](sources/x-twitter-automation.md) -- [2026-04-22] [Personal Knowledge Base (RAG)](sources/knowledge-base-rag.md) -- [2026-04-22] [Personal CRM with Automatic Contact Discovery](sources/personal-crm.md) -- [2026-04-22] [YouTube Content Pipeline](sources/youtube-content-pipeline.md) -- [2026-04-22] [Polymarket Autopilot](sources/polymarket-autopilot.md) -- [2026-04-22] [Goal-Driven Autonomous Tasks](sources/overnight-mini-app-builder.md) -- [2026-04-22] [Local CRM Framework with DenchClaw](sources/local-crm-framework.md) -- [2026-04-22] [OpenClaw + n8n Workflow Orchestration](sources/n8n-workflow-orchestration.md) -- [2026-04-22] [Multi-Channel AI Customer Service Platform](sources/multi-channel-customer-service.md) -- [2026-04-22] [Second Brain](sources/second-brain.md) -- [2026-04-22] [LaTeX Paper Writing](sources/latex-paper-writing.md) -- [2026-04-22] [Habit Tracker & Accountability Coach](sources/habit-tracker-accountability-coach.md) -- [2026-04-22] [Todoist Task Manager](sources/todoist-task-manager.md) -- [2026-04-22] [Dynamic Dashboard with Sub-agent Spawning](sources/dynamic-dashboard.md) -- [2026-04-22] [Pre-Build Idea Validator](sources/pre-build-idea-validator.md) -- [2026-04-22] [Autonomous Project Management with Subagents](sources/autonomous-project-management.md) -- [2026-04-22] [Daily Reddit Digest](sources/daily-reddit-digest.md) -- [2026-04-22] [Inbox De-clutter](sources/inbox-declutter.md) -- [2026-04-22] [Custom Morning Brief](sources/custom-morning-brief.md) -- [2026-04-22] [Market Research & Product Factory](sources/market-research-product-factory.md) -- [2026-04-22] [Phone-Based Personal Assistant](sources/phone-based-personal-assistant.md) -- [2026-04-22] [Event Guest Confirmation](sources/event-guest-confirmation.md) -- [2026-04-22] [Multi-Channel Personal Assistant](sources/multi-channel-assistant.md) -- [2026-04-22] [AI-Powered Earnings Tracker](sources/earnings-tracker.md) -- [2026-04-22] [Multi-Agent Specialized Team (Solo Founder Setup)](sources/multi-agent-team.md) -- [2026-04-22] [Project State Management System: Event-Driven Alternative to Kanban](sources/project-state-management.md) -- [2026-04-22] [Health & Symptom Tracker](sources/health-symptom-tracker.md) -- [2026-04-22] [Self-Healing Home Server & Infrastructure Management](sources/self-healing-home-server.md) -- [2026-04-22] [Multi-Agent Content Factory](sources/content-factory.md) -- [2026-04-22] [Daily YouTube Digest](sources/daily-youtube-digest.md) -- [2026-04-22] [Automated Meeting Notes & Action Items](sources/meeting-notes-action-items.md) -- [2026-04-22] [Podcast Production Pipeline](sources/podcast-production-pipeline.md) -- [2026-04-22] [Claude Code 调用方法总结](sources/claude-code调用方法总结.md) -- [2026-04-22] [N8N Full Tutorial Building AI Agents in 2025 for Beginners!](sources/n8n-full-tutorial-building-ai-agents-in-2025-for-beginners.md) -- [2026-04-22] [n8n + Claude：通过自然语言自动化工作流](sources/n8n-claude-通过自然语言自动化工作流.md) -- [2026-04-22] [万字保姆级教程，让你90天跑通一人公司模式（附AI提示词）](sources/万字保姆级教程-90天跑通一人公司模式-2026-03-29.md) -- [2026-04-22] [使用Claude自动生成N8N工作流的实操教程](sources/使用claude自动生成n8n工作流的实操教程.md) -- [2026-04-22] [MCP在Cursor中的集成与应用详解](sources/mcp在cursor中的集成与应用详解.md) -- [2026-04-22] [Google 5个 Agent Skill 设计模式](sources/google-5个agent-skill设计模式-2026-03-19.md) -- [2026-04-22] [n8n configure telegram trigger](sources/n8n-configure-telegram-trigger.md) -- [2026-04-22] [n8n Docker 安装与更新](sources/n8n-docker-install-update.md) -- [2026-04-22] [万字讲透OpenClaw Workspace深度解析](sources/万字讲透openclaw-workspace深度解析-2026-03-21.md) -- [2026-04-22] [How to get Youtube Channel ID](sources/how-to-get-youtube-channel-id.md) -- [2026-04-22] [TikTok PM - Python Django 项目](sources/tiktok-pm-python-django-project.md) -- [2026-04-22] [dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1](sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md) — (expected: wiki/sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md — source missing) -- [2026-04-22] [Obsidian 高效指南：我常用的插件与实用技巧](sources/obsidian-高效指南-我常用的插件与实用技巧.md) -- [2026-04-22] [Obsidian最有必要安装的10款插件是这些](sources/obsidian最有必要安装的10款插件是这些.md) -- [2026-04-22] [Obsidian Tasks 插件：这可能是最适合懒人的任务管理方式](sources/obsidian-tasks-插件-这可能是最适合懒人的任务管理方式.md) -- [2026-04-22] [ChinaTextbook - 41.53 GB，中国小学、初中、高中、大学 PDF 教材](sources/chinatextbook-41-53-gb-中国小学-初中-高中-大学-pdf-教材.md) -- [2026-04-22] [开发经验与项目规范整理文档](sources/开发经验与项目规范整理文档.md) -- [2026-04-22] [在Ubuntu上安装Vibe-Kanban](sources/在ubuntu上安装vibe-kanban.md) -- [2026-04-22] [Vibe-Kanban + OpenCode 在 Ubuntu Server 上安装与管理指南](sources/vibe-kanban-opencode-在-ubuntu-server-上安装与管理指南.md) -- [2026-04-22] [Vibe Coding 经验收集](sources/vibe-coding经验收集.md) -- [2026-04-22] [如何在项目里安装Claude Code Templates Skills](sources/如何在项目里安装claude-code-templates-skills.md) -- [2026-04-22] [Trae远程开发部署指南](sources/trae远程开发部署指南.md) -- [2026-04-22] [Cursor 2.0初学者使用指南](sources/cursor-2-0初学者使用指南.md) -- [2026-04-22] [如何在Ubuntu上安装OpenCode并配置Vibe-Kanban](sources/如何在ubuntu上安装opencode并配置vibe-kanban.md) -- [2026-04-22] [如何传输Docker images 并且在另一个Docker安装](sources/如何传输docker-images-并且在另一个docker安装.md) -- [2026-04-22] [Ubuntu用RustDesk远程登录出现不能使用Wayland登录的错误](sources/ubuntu用rustdesk远程登录出现不能使用wayland登录的错误.md) -- [2026-04-21] [用Docker安装Homarr](sources/用docker安装homarr.md) -- [2026-04-21] [在Ubuntu上通过VPS+内网反向代理实现域名访问内网穿透](sources/在ubuntu上通过vps-内网反向代理实现域名访问内网穿透.md) -- [2026-04-21] [如何在Ubuntu Server上通过NFS挂载Synology NAS上的共享文件夹](sources/如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹.md) -- [2026-04-21] [用Docker安装Apache Superset](sources/用docker安装apache-superset.md) -- [2026-04-21] [Mac Mini 服务器配置：防止自动锁屏与睡眠](sources/mac-mini-服务器配置-防止自动锁屏与睡眠.md) -- [2026-04-21] [家庭网络环境概览](sources/家庭网络环境概览_2026-04-03.md) -- [2026-04-21] [如何删除旧的废弃的Docker Container + Volume](sources/如何删除旧的废弃的docker-container-volume.md) -- [2026-04-21] [用Docker安装Portainer](sources/用docker安装portainer.md) -- [2026-04-21] [用Docker安装Jellyfin](sources/用docker安装jellyfin.md) -- [2026-04-21] [Ubuntu Server科学上网](sources/ubuntu-server科学上网.md) -- [2026-04-21] [Ubuntu禁用合盖休眠](sources/ubuntu禁用合盖休眠.md) -- [2026-04-21] [安装v2rayN](sources/安装v2rayn.md) -- [2026-04-21] [Install Apache Superset in Docker](sources/install-apache-superset-in-docker.md) -- [2026-04-21] [MinIO + Zipline 自托管图床应用安装教程](sources/minio-zipline-自托管图床应用安装教程.md) -- [2026-04-21] [群晖NAS科学上网方法](sources/群晖nas科学上网方法.md) -- [2026-04-21] [NodeWarden - 把 Bitwarden 搬上 Cloudflare Workers，彻底告别服务器](sources/nodewarden-把-bitwarden-搬上-cloudflare-workers-彻底告别服务器.md) -- [2026-04-21] [macOS 创建与解除 Symbolic Link（OpenClaw 目录映射）](sources/macos-创建与解除-symbolic-link-openclaw-目录映射.md) -- [2026-04-21] [如何在Ubuntu Server安装 Docker & Docker Compose](sources/如何在ubuntu-server安装-docker-docker-compose.md) -- [2026-04-21] [家庭监控方案：Prometheus + Grafana + Node Exporter + cAdvisor + Blackbox](sources/家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox.md) -- [2026-04-21] [Ubuntu 安装 FRP 0.65.0（x86_64）操作笔记](sources/ubuntu-安装-frp-0-65-0-x86_64-操作笔记.md) -- [2026-04-21] [Mac Mini 安装 FRP 0.65.0（ARM64）操作笔记](sources/mac-mini-安装-frp-0-65-0-arm64-操作笔记.md) -- [2026-04-21] [在Synology NAS上安装CloudDrive2](sources/在synology-nas上安装clouddrive2.md) -- [2026-04-21] [如何判别你的Linux 服务器是 x64（也就是 x86_64）还是 ARM64](sources/如何判别你的linux-服务器是-x64-也就是-x86_64-还是-arm64.md) -- [2026-04-21] [如何用指纹浏览器安全注册并订阅Claude Pro会员全攻略](sources/如何用指纹浏览器安全注册并订阅claude-pro会员全攻略.md) -- [2026-04-21] [安装Ubuntu 24.04.2在HP ZBook工作站笔记本上](sources/安装ubuntu-24-04-2在hp-zbook工作站笔记本上.md) -- [2026-04-21] [用Docker安装it-tools](sources/用docker安装it-tools.md) -- [2026-04-21] [通过VPS+内网反向代理实现域名访问内网穿透](sources/通过vps-内网反向代理实现域名访问内网穿透.md) -- [2026-04-21] [Clonezilla对Ubuntu Server进行全盘镜像备份](sources/clonezilla对ubuntu-server进行全盘镜像备份.md) -- [2026-04-21] [3X-UI Xray on BandwagonVPS](sources/3x-ui-xray-on-bandwagonvps.md) -- [2026-04-21] [Ubuntu 24.04 启动 SSH 服务](sources/ubuntu-24-04-enable-ssh.md) -- [2026-04-21] [用Docker安装transmission](sources/用docker安装transmission.md) -- [2026-04-21] [RAX50 路由器更新Merlin Clash订阅](sources/rax50-路由器-更新merlin-clash订阅.md) -- [2026-04-21] [网件RAX50路由器刷梅林固件与科学上网插件安装教程](sources/网件rax50路由器刷梅林固件与科学上网插件安装教程.md) -- [2026-04-21] [MySQL MariaDB 数据库详细信息](sources/mysql-mariadb-数据库详细信息.md) -- [2026-04-21] [Ubuntu服务器通过rsync实现日常增量备份](sources/ubuntu服务器通过rsync实现日常增量备份.md) -- [2026-04-21] [Linux 运维必会的 150 个命令](sources/linux-运维必会的-150-个命令.md) -- [2026-04-21] [用Docker中安装Navidrome](sources/用docker中安装navidrome.md) -- [2026-04-21] [Cloud Operating Model: Key Strategies and Best Practices](sources/cloud-operating-model-key-strategies-and-best-practices.md) -- [2026-04-21] [What is DevSecOps? Best Practices, Benefits, and Tools](sources/what-is-devsecops-best-practices-benefits-and-tools.md) -- [2026-04-21] [Modern ITSM: Driving Efficiency, Security & Resilience](sources/understanding-complete-itsm.md) -- [2026-04-21] [How to Simplify Multi-Account Deployments Monitoring: Centralized Logs for AWS CloudFormation StackSets](sources/how-to-simplify-multi-account-deployments-monitoring-centralized-logs-for-aws-cloudformation-stacksets.md) -- [2026-04-21] [RTO vs RPO: Key Differences for Modern Disaster Recovery](sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md) -- [2026-04-21] [These 6 Linux Apps Let You Monitor System Resources in Style](sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md) -- [2026-04-21] [Public vs Private vs Hybrid Cloud Differences Explained](sources/public-vs-private-vs-hybrid-cloud-differences-explained.md) -- [2026-04-21] [How Agentic AI can help for Cloud DevOps](sources/how-agentic-ai-can-help-for-cloud-devops.md) -- [2026-04-21] [The Myths and Misconceptions About Cloud Computing | LinkedIn](sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md) -- [2026-04-21] [Cloud Maturity Model - A Detailed Guide For Cloud Adoption](sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md) -- [2026-04-21] [DevOps Maturity Model From Traditional IT to Advanced DevOps](sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md) -- [2026-04-21] [How Can a Multi Cloud Strategy Transform Your Business ROI?](sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md) -- [2026-04-21] [What I Know About Cloud Service Delivery 1](sources/what-i-know-about-cloud-service-delivery-1.md) -- [2026-04-21] [Cloud DevOp Maturity - Guideline](sources/cloud-devop-maturity-guideline.md) -- [2026-04-21] [DevOps Culture and Transformation: Fostering Collaboration, Agile Practices, and Innovation](sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md) -- [2026-04-20] [security](sources/security.md) — (expected: wiki/sources/security.md — source missing) -- [2026-04-20] [llm-wiki](sources/llm-wiki.md) — (expected: wiki/sources/llm-wiki.md — source missing) -- [2026-04-20] [baoyu-skills](sources/baoyu-skills.md) — (expected: wiki/sources/baoyu-skills.md — source missing) -- [Your-AI-Isn-t-Stupid---It-Just-Needs-a-Better-Harness--Lychee-Technology-Engineering-Blog](sources/Your-AI-Isn-t-Stupid---It-Just-Needs-a-Better-Harness--Lychee-Technology-Engineering-Blog.md) — (expected: wiki/sources/Your-AI-Isn-t-Stupid---It-Just-Needs-a-Better-Harness--Lychee-Technology-Engineering-Blog.md — source missing) -- [Expose-hermes-agent-as-an-OpenAI-compatible-API-for-any-frontend](sources/Expose-hermes-agent-as-an-OpenAI-compatible-API-for-any-frontend.md) — (expected: wiki/sources/Expose-hermes-agent-as-an-OpenAI-compatible-API-for-any-frontend.md — source missing) -- [n8n-调用openclaw-agents的工作流架构](sources/n8n-调用openclaw-agents的工作流架构.md) — (expected: wiki/sources/n8n-调用openclaw-agents的工作流架构.md — source missing) +- [2023-10-30] [What is DevSecOps? Best Practices, Benefits, and Tools](sources/what-is-devsecops-best-practices-benefits-and-tools.md) — DevSecOps 将安全嵌入 SDLC 全流程，实现全员安全责任与自动化工具链 +- [2026-04-26] [Modern ITSM: Driving Efficiency, Security & Resilience](sources/understanding-complete-itsm.md) +- [2026-04-26] [How to Simplify Multi-Account Deployments Monitoring: Centralized Logs for AWS CloudFormation StackSets](sources/how-to-simplify-multi-account-deployments-monitoring-centralized-logs-for-aws-cloudformation-stacksets.md) +- [2026-04-26] [RTO vs RPO: Key Differences for Modern Disaster Recovery](sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md) +- [2026-04-26] [These 6 Linux Apps Let You Monitor System Resources in Style](sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md) +- [2026-04-26] [Public vs Private vs Hybrid Cloud Differences Explained](sources/public-vs-private-vs-hybrid-cloud-differences-explained.md) +- [2026-04-26] [How Agentic AI can help for Cloud DevOps](sources/how-agentic-ai-can-help-for-cloud-devops.md) +- [2026-04-26] [DevOps Maturity Model From Traditional IT to Advanced DevOps](sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md) +- [2026-04-26] [How Can a Multi Cloud Strategy Transform Your Business ROI?](sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md) +- [2026-04-26] [The Myths and Misconceptions About Cloud Computing | LinkedIn](sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md) +- [2026-04-26] [What I Know About Cloud Service Delivery 1](sources/what-i-know-about-cloud-service-delivery-1.md) +- [2026-04-26] [Cloud Maturity Model - A Detailed Guide For Cloud Adoption](sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md) +- [2026-04-26] [Cloud DevOp Maturity - Guideline](sources/cloud-devop-maturity-guideline.md) +- [2026-04-26] [DevOps Culture and Transformation: Fostering Collaboration, Agile Practices, and Innovation](sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md) +- [超达物流定价](sources/超达物流定价.md) +- [电商视频Prompt库](sources/电商视频prompt.md) +- [电商如何选品 - 如何找到爆款选品策略](sources/电商如何选品-如何找到爆款-选品策略.md) +- [做TK跨境思路不对努力白费](sources/做tk跨境思路不对努力白费.md) +- [TikTok Shop - Apache Superset Dashboard设计思路](sources/tiktok-shop-apache-superset-dashboard设计思路.md) +- [TK美国面单授权及操作流程](sources/tk美国面单授权及操作流程.md) +- [Scrapy + Playwright 抓取TikTok Shop Data](sources/scrapy-playwright-抓取tiktok-shop-data.md) +- [养龙虾5天血泪史：我的AI Agent为什么总失忆？OpenClaw 记忆调试全记录](sources/养龙虾5天血泪史-我的ai-agent为什么总失忆-openclaw-记忆调试全记录.md) +- [养虾日记5：深夜与苏轼聊AI，他说：被浪打下去还能爬起来的才叫风流](sources/养虾日记5-深夜与苏轼聊ai-他说-被浪打下去还能爬起来的才叫风流.md) +- [养虾日记4：一次「Context Limit Exceeded」错误排查：我以为是小问题，结果踩了大坑](sources/养虾日记4-一次「context-limit-exceeded」错误排查-我以为是小问题-结果踩了大坑.md) +- [养虾日记3：用 Obsidian + Gitea 为 AI 助手构建持久化笔记系统](sources/养虾日记3-用-obsidian-gitea-为-ai-助手构建持久化笔记系统.md) +- [养虾日记2：让Agent更懂你：OpenClaw + Self-Improving 复盘实战案例分享](sources/养虾日记2-让agent更懂你-openclaw-self-improving-复盘实战案例分享.md) +- [养虾日记1：我用 OpenClaw 管了 28 万张照片：一次真实的多设备照片整理实战](sources/养虾日记1-我用-openclaw-管了-28-万张照片-一次真实的多设备照片整理实战.md) +- [不谈技术：普通人该怎么在AI时代赚钱？](sources/不谈技术-普通人该怎么在ai时代赚钱.md) +- [开发经验与项目规范整理文档](sources/开发经验与项目规范整理文档.md) +- [如何在项目里安装Claude Code Templates Skills](sources/如何在项目里安装claude-code-templates-skills.md) +- [如何在Ubuntu上安装OpenCode并配置Vibe-Kanban](sources/如何在ubuntu上安装opencode并配置vibe-kanban.md) +- [在Ubuntu上安装Vibe-Kanban](sources/在ubuntu上安装vibe-kanban.md) +- [Vibe Coding 经验收集](sources/vibe-coding经验收集.md) +- [Vibe-Kanban + OpenCode 在 Ubuntu Server 上安装与管理指南](sources/vibe-kanban-opencode-在-ubuntu-server-上安装与管理指南.md) +- [Trae远程开发部署指南](sources/trae远程开发部署指南.md) +- [Cursor 2.0初学者使用指南](sources/cursor-2-0初学者使用指南.md) +- [我做了个 Skill：让 AI 帮你生成 Logo 和图标](sources/我做了个-skill-让-ai-帮你生成-logo-和图标.md) +- [fireworks-tech-graph](sources/fireworks-tech-graph.md) +- [Blogwatcher Daily 技能收藏](sources/blogwatcher-daily收藏.md) +- [baoyu-skills](sources/baoyu-skills.md) — (expected: wiki/sources/baoyu-skills.md — source missing) +- [Obsidian 必装 Skills](sources/obsidian-必装-skills.md) +- [Obsidian 官方 CLI 命令全景速查表](sources/obsidian-官方-cli-命令全景速查表.md) +- [Obsidian CLI](sources/obsidian-cli.md) +- [Last30Days 使用指南](sources/last30days-使用指南.md) +- [GOG CLI 安装配置指南](sources/gog-cli-安装配置指南.md) +- [可自动化、可扩展、AI增强的电商数据采集与处理系统](sources/可自动化-可扩展-ai增强的电商数据采集与处理系统.md) +- [TikTok PM - Python Django 项目](sources/tiktok-pm-python-django-project.md) +- [Obsidian最有必要安装的10款插件是这些](sources/obsidian最有必要安装的10款插件是这些.md) +- [Obsidian 高效指南：我常用的插件与实用技巧](sources/obsidian-高效指南-我常用的插件与实用技巧.md) +- [Obsidian Tasks 插件：这可能是最适合懒人的任务管理方式](sources/obsidian-tasks-插件-这可能是最适合懒人的任务管理方式.md) +- [How to get Youtube Channel ID](sources/how-to-get-youtube-channel-id.md) +- [dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1](sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md) — (expected: wiki/sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md — source missing) +- [ChinaTextbook - 41.53 GB，中国小学、初中、高中、大学 PDF 教材](sources/chinatextbook-41-53-gb-中国小学-初中-高中-大学-pdf-教材.md) +- [通过VPS+内网反向代理实现域名访问内网穿透](sources/通过vps-内网反向代理实现域名访问内网穿透.md) +- [群晖NAS科学上网方法](sources/群晖nas科学上网方法.md) +- [网件RAX50路由器刷梅林固件与科学上网插件安装教程](sources/网件rax50路由器刷梅林固件与科学上网插件安装教程.md) +- [用Docker安装transmission](sources/用docker安装transmission.md) +- [用Docker安装it-tools](sources/用docker安装it-tools.md) +- [用Docker安装Portainer](sources/用docker安装portainer.md) +- [用Docker安装Jellyfin](sources/用docker安装jellyfin.md) +- [用Docker安装Homarr](sources/用docker安装homarr.md) +- [用Docker安装Apache Superset](sources/用docker安装apache-superset.md) +- [用Docker中安装Navidrome](sources/用docker中安装navidrome.md) +- [家庭网络环境概览](sources/家庭网络环境概览_2026-04-03.md) +- [家庭监控方案：Prometheus + Grafana + Node Exporter + cAdvisor + Blackbox](sources/家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox.md) +- [实战笔记：本地部署 RSSHub 并获取 YouTube 订阅](sources/实战笔记-本地部署-rsshub-并获取-youtube-订阅.md) +- [安装v2rayN](sources/安装v2rayn.md) +- [安装Ubuntu 24.04.2在HP ZBook工作站笔记本上](sources/安装ubuntu-24-04-2在hp-zbook工作站笔记本上.md) +- [如何用指纹浏览器安全注册并订阅Claude Pro会员全攻略](sources/如何用指纹浏览器安全注册并订阅claude-pro会员全攻略.md) +- [如何在Ubuntu Server安装 Docker & Docker Compose](sources/如何在ubuntu-server安装-docker-docker-compose.md) +- [如何在Ubuntu Server上通过NFS挂载Synology NAS上的共享文件夹](sources/如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹.md) +- [如何判别你的Linux 服务器是 x64（也就是 x86_64）还是 ARM64](sources/如何判别你的linux-服务器是-x64-也就是-x86_64-还是-arm64.md) +- [如何删除旧的废弃的Docker Container + Volume](sources/如何删除旧的废弃的docker-container-volume.md) +- [如何传输Docker images 并且在另一个Docker安装](sources/如何传输docker-images-并且在另一个docker安装.md) +- [在Ubuntu上通过VPS+内网反向代理实现域名访问内网穿透](sources/在ubuntu上通过vps-内网反向代理实现域名访问内网穿透.md) +- [在Synology NAS上安装CloudDrive2](sources/在synology-nas上安装clouddrive2.md) - [n8n-docker-配置-telegram-代理-troubleshooting](sources/n8n-docker-配置-telegram-代理-troubleshooting.md) — (expected: wiki/sources/n8n-docker-配置-telegram-代理-troubleshooting.md — source missing) -- [n8n调用hermes-agents的工作流架构](sources/n8n调用hermes-agents的工作流架构.md) — (expected: wiki/sources/n8n调用hermes-agents的工作流架构.md — source missing) -- [open-webui-hermes-agent](sources/open-webui-hermes-agent.md) — (expected: wiki/sources/open-webui-hermes-agent.md — source missing) -- [language-translator](sources/language-translator.md) — (expected: wiki/sources/language-translator.md — source missing) -- [loan-officer-assistant](sources/loan-officer-assistant.md) — (expected: wiki/sources/loan-officer-assistant.md — source missing) -- [real-estate-buyer-seller](sources/real-estate-buyer-seller.md) — (expected: wiki/sources/real-estate-buyer-seller.md — source missing) -- [legal-document-review](sources/legal-document-review.md) — (expected: wiki/sources/legal-document-review.md — source missing) -- [sales-outreach](sources/sales-outreach.md) — (expected: wiki/sources/sales-outreach.md — source missing) -- [retail-customer-returns](sources/retail-customer-returns.md) — (expected: wiki/sources/retail-customer-returns.md — source missing) -- [specialized-chief-of-staff](sources/specialized-chief-of-staff.md) — (expected: wiki/sources/specialized-chief-of-staff.md — source missing) -- [hr-onboarding](sources/hr-onboarding.md) — (expected: wiki/sources/hr-onboarding.md — source missing) -- [customer-service](sources/customer-service.md) — (expected: wiki/sources/customer-service.md — source missing) -- [healthcare-customer-service](sources/healthcare-customer-service.md) — (expected: wiki/sources/healthcare-customer-service.md — source missing) -- [legal-billing-time-tracking](sources/legal-billing-time-tracking.md) — (expected: wiki/sources/legal-billing-time-tracking.md — source missing) -- [legal-client-intake](sources/legal-client-intake.md) — (expected: wiki/sources/legal-client-intake.md — source missing) -- [hospitality-guest-services](sources/hospitality-guest-services.md) — (expected: wiki/sources/hospitality-guest-services.md — source missing) -- [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [marketing-agentic-search-optimizer](sources/marketing-agentic-search-optimizer.md) — (expected: wiki/sources/marketing-agentic-search-optimizer.md — source missing) -- [Examples - Agency Multi-Agent Collaboration Showcase](sources/readme.md) -- [finance-bookkeeper-controller](sources/finance-bookkeeper-controller.md) — (expected: wiki/sources/finance-bookkeeper-controller.md — source missing) -- [finance-fpa-analyst](sources/finance-fpa-analyst.md) — (expected: wiki/sources/finance-fpa-analyst.md — source missing) -- [finance-investment-researcher](sources/finance-investment-researcher.md) — (expected: wiki/sources/finance-investment-researcher.md — source missing) -- [finance-financial-analyst](sources/finance-financial-analyst.md) — (expected: wiki/sources/finance-financial-analyst.md — source missing) -- [finance-tax-strategist](sources/finance-tax-strategist.md) — (expected: wiki/sources/finance-tax-strategist.md — source missing) -- [engineering-voice-ai-integration-engineer](sources/engineering-voice-ai-integration-engineer.md) — (expected: wiki/sources/engineering-voice-ai-integration-engineer.md — source missing) -- [engineering-codebase-onboarding-engineer](sources/engineering-codebase-onboarding-engineer.md) — (expected: wiki/sources/engineering-codebase-onboarding-engineer.md — source missing) -- [engineering-minimal-change-engineer](sources/engineering-minimal-change-engineer.md) — (expected: wiki/sources/engineering-minimal-change-engineer.md — source missing) +- [macOS 创建与解除 Symbolic Link（OpenClaw 目录映射）](sources/macos-创建与解除-symbolic-link-openclaw-目录映射.md) +- [WSL2 启动与网络配置指南](sources/wsl2-启动与网络配置指南.md) +- [Ubuntu禁用合盖休眠](sources/ubuntu禁用合盖休眠.md) +- [Ubuntu用RustDesk远程登录出现不能使用Wayland登录的错误](sources/ubuntu用rustdesk远程登录出现不能使用wayland登录的错误.md) +- [Ubuntu服务器通过rsync实现日常增量备份](sources/ubuntu服务器通过rsync实现日常增量备份.md) +- [Ubuntu 安装 FRP 0.65.0（x86_64）操作笔记](sources/ubuntu-安装-frp-0-65-0-x86_64-操作笔记.md) +- [Ubuntu Server科学上网](sources/ubuntu-server科学上网.md) +- [Ubuntu 24.04 启动 SSH 服务](sources/ubuntu-24-04-enable-ssh.md) +- [RAX50 路由器更新Merlin Clash订阅](sources/rax50-路由器-更新merlin-clash订阅.md) +- [NodeWarden - 把 Bitwarden 搬上 Cloudflare Workers，彻底告别服务器](sources/nodewarden-把-bitwarden-搬上-cloudflare-workers-彻底告别服务器.md) +- [MySQL MariaDB 数据库详细信息](sources/mysql-mariadb-数据库详细信息.md) +- [MinIO + Zipline 自托管图床应用安装教程](sources/minio-zipline-自托管图床应用安装教程.md) +- [Mac必装软件清单](sources/mac必装软件清单-2026-04-17.md) +- [Mac Mini 服务器配置：防止自动锁屏与睡眠](sources/mac-mini-服务器配置-防止自动锁屏与睡眠.md) +- [Mac Mini 安装 FRP 0.65.0（ARM64）操作笔记](sources/mac-mini-安装-frp-0-65-0-arm64-操作笔记.md) +- [Linux 运维必会的 150 个命令](sources/linux-运维必会的-150-个命令.md) +- [Install WSL](sources/install-wsl.md) +- [Install Apache Superset in Docker](sources/install-apache-superset-in-docker.md) +- [Clonezilla对Ubuntu Server进行全盘镜像备份](sources/clonezilla对ubuntu-server进行全盘镜像备份.md) +- [Building your Quartz](sources/building-your-quartz.md) +- [3X-UI Xray on BandwagonVPS](sources/3x-ui-xray-on-bandwagonvps.md) +- [What is DevSecOps? Best Practices, Benefits, and Tools](sources/what-is-devsecops-best-practices-benefits-and-tools.md) - [sre-weekly-issue-513](sources/sre-weekly-issue-513.md) — (expected: wiki/sources/sre-weekly-issue-513.md — source missing) -- [karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环](sources/karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环.md) — (expected: wiki/sources/karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环.md — source missing) -- [如何让ai生成风格一致的图片](sources/如何让ai生成风格一致的图片.md) — (expected: wiki/sources/如何让ai生成风格一致的图片.md — source missing) +- [Cloud Learning Master Index](sources/cloud-learning-master-index.md) +- [Public Cloud Learning Sessions - Tagging Standards for All Hyperscalers - 20240123](sources/public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123-1.md) +- [Public Cloud Learning Sessions (OpenText) - Thor Platform & Flows](sources/public-cloud-learning-sessions-opentext-thor-platform-flows-20241210-160056-meet.md) +- [Public Cloud Learning Sessions - OpenText Tagging Standard v2 - 20250429](sources/public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meet.md) +- [Public Cloud Learning Sessions (OpenText) - Product Hub (PHT) Overview and Q&A - 20240806](sources/public-cloud-learning-sessions-opentext-product-hub-pht-overview-and-qa-20240806.md) +- [Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab Migration](sources/public-cloud-learning-sessions-opentext-github-enterprise-to-gitlab-migration-20.md) +- [Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723](sources/public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2.md) +- [Public Cloud Learning Sessions - AWS End User Compute Services - 20240430](sources/public-cloud-learning-sessions-aws-end-user-compute-services-20240430-160120-mee.md) +- [Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109](sources/public-cloud-learning-sessions-applicable-business-analysis-techniques-20240109.md) +- [CTP Topic 65 Tracing the Value Delivered in Cloud Transformation](sources/ctp-topic-65-tracing-the-value-delivered-in-cloud-transformation.md) +- [CTP Topic 6 AWS Workspaces Demo](sources/ctp-topic-6-aws-workspaces-demo.md) +- [CTP Topic 57 Product backlog managing demand](sources/ctp-topic-57-product-backlog-managing-demand.md) +- [CTP Topic 53 Why bother with Cloud](sources/ctp-topic-53-why-bother-with-cloud.md) +- [CTP Topic 41 NFR's and Error Budgets](sources/ctp-topic-41-nfrs-and-error-budgets.md) +- [CTP Topic 4 Using Agile to Run the Cloud Transformation Programme](sources/ctp-topic-4-using-agile-to-run-the-cloud-transformation-program.md) +- [CTP Topic 30 Managing Change](sources/ctp-topic-30-managing-change.md) +- [CTP Topic 23 Introduction to the Technical Architecture Team and Function](sources/ctp-topic-23-introduction-to-the-technical-architecture-team-and-function.md) +- [CTP Topic 20 Program demand process flow and PoC onboarding](sources/ctp-topic-20-program-demand-process-flow-and-poc-onboarding.md) +- [CTP Topic 10 AWS Landing Zone (LZ) Data Collection, Tagging Related Security](sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md) +- [Public Cloud Learning Sessions - Serverless Computing - 20240903](sources/public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee.md) +- [Public Cloud Learning Sessions (OpenText) - Generative AI & Prompt Engineering - 20241112](sources/public-cloud-learning-sessions-opentext-generative-ai-prompt-engineering-2024111.md) +- [Public Cloud Learning Sessions (OpenText) - Event Driven Architecture Part 2](sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091.md) +- [Public Cloud Learning Sessions (OpenText) - Event Driven Architecture Part 1](sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091.md) +- [Public Cloud Learning Sessions (OpenText) - AI Use Cases - 20241126 160106](sources/public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec.md) +- [Public Cloud Learning Sessions - Introduction to AI/ML with AWS](sources/public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin.md) +- [CTP Topic 69 Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on AWS](sources/ctp-topic-69-best-practices-for-migrating-on-premises-iod-virtual-machines-to-vm.md) +- [CTP Topic 61 Workload VPC provision with IPAM Automation](sources/ctp-topic-61-workload-vpc-provision-with-ipam-automation.md) +- [CTP Topic 45 Automatic IP address allocation with IPAM](sources/ctp-topic-45-automatic-ip-address-allocation-with-ipam.md) +- [CTP Topic 43 VMware Cloud on AWS](sources/ctp-topic-43-vmware-cloud-on-aws.md) +- [CTP Topic 36 SendGrid as an Email Service](sources/ctp-topic-36-sendgrid-as-an-email-service.md) +- [CTP Topic 31 Network Segregation and Secure Access to the New AWS Landing Zones](sources/ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones.md) +- [CTP Topic 22 Global DNS service offerings](sources/ctp-topic-22-global-dns-service-offerings.md) +- [CTP Topic 19 Configuring DNS within AWS LZs](sources/ctp-topic-19-configuring-dns-within-aws-lzs.md) +- [CTP Topic 18 Wide Area Networking in AWS Cloud](sources/ctp-topic-18-wide-area-networking-in-aws-cloud.md) +- [Public Cloud Learning Sessions - OpenText GIS Security Policies - 20241015](sources/public-cloud-learning-sessions-opentext-gis-security-policies-20241015-160257-me.md) +- [CTP Topic 62 AWS Secrets Manager](sources/ctp-topic-62-aws-secrets-manager.md) +- [CTP Topic 55 AWS Firewall Manager](sources/ctp-topic-55-aws-firewall-manager.md) +- [CTP Topic 52 3 Lines of Defence (3LoD) framework Cloud Security Posture Management (CSPM)](sources/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md) +- [CTP Topic 49 Container Lifecycle Hardening Standards](sources/ctp-topic-49-container-lifecycle-hardening-standards.md) +- [CTP Topic 37 Secrets Certificates Management](sources/ctp-topic-37-secrets-certificates-management.md) +- [CTP Topic 24 Micro Focus Product Privacy Framework](sources/ctp-topic-24-micro-focus-product-privacy-framework.md) +- [CTP Topic 21 Supply Chain Security in Micro Focus](sources/ctp-topic-21-supply-chain-security-in-micro-focus.md) +- [Public Cloud Learning Sessions - Ollie Workflow and The Demand Process - 20240416](sources/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md) +- [CTP Topic 9 CI CD with Gruntwork](sources/ctp-topic-9-ci-cd-with-gruntwork.md) +- [CTP Topic 56 Automated Infrastructure Testing](sources/ctp-topic-56-automated-infrastructure-testing.md) +- [CTP Topic 33 An Introduction to GitOps](sources/ctp-topic-33-an-introduction-to-gitops.md) +- [CTP Topic 32 Using Atlantis CICD for Infrastructure Deployments](sources/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md) +- [CTP Topic 3 Deploy and maintain infrastructure](sources/ctp-topic-3-deploy-and-maintain-infrastructure.md) +- [CTP Topic 2 Git](sources/ctp-topic-2-git.md) +- [CTP Topic 15 Working with Renovatebot](sources/ctp-topic-15-working-with-renovatebot.md) +- [Public Cloud Learning Sessions - Storage Cost Optimization - 20240305](sources/public-cloud-learning-sessions-storage-cost-optimization-20240305-160037-meeting.md) +- [Public Cloud Learning Sessions - Reducing Cloud Costs - 20250318](sources/public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco.md) +- [Public Cloud Learning Sessions - Budget Control - 20240319](sources/public-cloud-learning-sessions-budget-control-20240319-160204-meeting-recording.md) +- [Public Cloud Learning Sessions - Best practices for EC2 cost optimization in AWS - 20240529](sources/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md) +- [CTP Topic 71 PCG's guide to RightSizing, why, how when](sources/ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when.md) +- [CTP Topic 63 Optimise resource cost using automation](sources/ctp-topic-63-optimise-resource-cost-using-automation.md) +- [CTP Topic 27 AWS Instance Scheduler](sources/ctp-topic-27-aws-instance-scheduler.md) +- [CTP Topic 13 Cloud FinOps Micro Focus Policies best practices to optimize the costs](sources/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md) +- [Public Cloud Learning Sessions - Observability with OpenTelemetry - 20240402](sources/public-cloud-learning-sessions-observability-with-opentelemetry-20240402-160113.md) +- [Public Cloud Learning Sessions - EKS Optimization Part 3 of 3 - Introduction to EKS Auto Mode](sources/public-cloud-learning-sessions-eks-optimization-part-3-of-3-introduction-to-eks.md) +- [Public Cloud Learning Sessions - EKS Optimization Part 2 of 3 - Running Containers with Bottlerocket OS](sources/public-cloud-learning-sessions-eks-optimization-part-2-of-3-running-containers-w.md) +- [Public Cloud Learning Sessions - EKS Optimization Part 1 of 3 - Compute Optimization with Karpenter](sources/public-cloud-learning-sessions-eks-optimization-part-1-of-3-compute-optimization.md) +- [CTP Topic 8 - Implementation of Cloud Monitoring using Micro Focus Operations Bridge Manager](sources/ctp-topic-8-implementation-of-cloud-monitoring-using-micro-focus-operations-brid.md) +- [CTP Topic 70 EKS deployment using IAC](sources/ctp-topic-70-eks-deployment-using-iac.md) +- [CTP Topic 67 Cloud native observability using OpenTelemetry](sources/ctp-topic-67-cloud-native-observability-using-opentelemetry.md) +- [CTP Topic 64 Scaling out with Amazon EKS](sources/ctp-topic-64-scaling-out-with-amazon-eks.md) +- [CTP Topic 60 - Monitor AWS using Hyperscale Observability with Grafana](sources/ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana.md) +- [CTP Topic 59 Achieving reliability with Amazon EKS](sources/ctp-topic-59-achieving-reliability-with-amazon-eks.md) +- [CTP Topic 54 ESM SaaS Log Analytics](sources/ctp-topic-54-esm-saas-log-analytics.md) +- [CTP Topic 42 Grafana Observability Dashboard](sources/ctp-topic-42-grafana-observability-dashboard.md) +- [CTP Topic 39 Implementing EKS in the AWS Lab Landing Zone](sources/ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone.md) +- [CTP Topic 29 Cloud Monitoring – SaaS LZ accounts](sources/ctp-topic-29-cloud-monitoring-saas-lz-accounts.md) +- [Learning Sessions ECS Deployment using IAC - 20230808](sources/learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording.md) +- [Learning Sessions Cloud Transformation Programme-Deploying RDS via Terraform](sources/learning-sessions-cloud-transformation-programme-deploying-rds-via-terraform.md) +- [Learning Sessions Cloud Transformation Programme-20230808 183322-Meeting Recording](sources/learning-sessions-cloud-transformation-programme-20230808-183322-meeting-recordi.md) +- [CTP Topic 48 Terraform vs Terragrunt](sources/ctp-topic-48-terraform-vs-terragrunt.md) +- [CTP Topic 16 Cross-account Terraform modules](sources/ctp-topic-16-cross-account-terraform-modules.md) +- [CTP Topic 12 Using SES SMTP service terraform module](sources/ctp-topic-12-using-ses-smtp-service-terraform-module.md) +- [Learning Sessions Identity Governance VSM Replacement - 20231128](sources/learning-sessions-identity-governance-vsm-replacement-20231128-160326-meeting-re.md) +- [CTP Topic 5 - AWS Identity and Access Management (IAM)](sources/ctp-topic-5-aws-identity-and-access-management-iam.md) +- [CTP Topic 11 AD Integration and Login using AD Accounts](sources/ctp-topic-11-ad-integration-and-login-using-ad-accounts.md) +- [Learning Sessions: Standard AMI Updates 20231205](sources/learning-sessions-standard-amis-updates-20231205-160324-meeting-recording-2.md) +- [CTP Topic 73 AWS Backup Implementation of the Cloud Transformation Programme](sources/ctp-topic-73-aws-backup-implementation-of-the-cloud-transformation-program.md) +- [CTP Topic 72 Implementing an Enterprise DR Strategy Using AWS Backup](sources/ctp-topic-72-implementing-an-enterprise-dr-strategy-using-aws-backup.md) +- [CTP Topic 7 SaaS Landing Zone Design](sources/ctp-topic-7-saas-landing-zone-design.md) +- [CTP Topic 68 Introduction to Redshift](sources/ctp-topic-68-introduction-to-redshift.md) +- [CTP Topic 66 Exposing the differences between PostgreSQL RDS and Aurora](sources/ctp-topic-66-exposing-the-differences-between-postgresql-rds-and-aurora.md) +- [CTP Topic 58 AWS EC2 Image Builder](sources/ctp-topic-58-aws-ec2-image-builder.md) +- [CTP Topic 51 Architecting with AWS Purpose-Built Databases](sources/ctp-topic-51-architecting-with-aws-purpose-built-databases.md) +- [CTP Topic 50 AMI Roadmap for AWS AMIs](sources/ctp-topic-50-ami-roadmap-for-aws-amis.md) +- [CTP Topic 47 Enterprise Architecture Cloud Standards](sources/ctp-topic-47-enterprise-architecture-cloud-standards.md) +- [CTP Topic 46 NetApps on AWS](sources/ctp-topic-46-netapps-on-aws.md) +- [CTP Topic 44 AWS Backup in Micro Focus](sources/ctp-topic-44-aws-backup-in-micro-focus.md) +- [CTP Topic 40 SaaS Database Architecture On AWS Cloud](sources/ctp-topic-40-saas-database-architecture-on-aws-cloud.md) +- [CTP Topic 35 AWS Landing Zone Design Refresher (SaaS Labs)](sources/ctp-topic-35-aws-landing-zone-design-refresher-saas-labs.md) +- [CTP Topic 34 Azure Landing Zone Architecture Overview](sources/ctp-topic-34-azure-landing-zone-architecture-overview.md) +- [CTP Topic 28 AWS Tag Validation Tool](sources/ctp-topic-28-aws-tag-validation-tool.md) +- [CTP Topic 26 Standard AMI – build, publish, share processes](sources/ctp-topic-26-standard-ami-build-publish-share-processes.md) +- [CTP Topic 25 Labs Landing Zone Overview - ITOM Teams](sources/ctp-topic-25-labs-landing-zone-overview-itom-teams.md) +- [CTP Topic 17 Active Directory Services in Gruntwork AWS LZs](sources/ctp-topic-17-active-directory-services-in-gruntwork-aws-lzs.md) +- [CTP Topic 14 Octane Hub on AWS Real Life Experience Moving Production Services](sources/ctp-topic-14-octane-hub-on-aws-real-life-experience-moving-production-services-i.md) +- [CTP Topic 10 AWS Landing Zone (LZ) Data Collection, Tagging Related Security](sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md) +- [CTP Topic 1 Gruntwork Landing Zone Architecture](sources/ctp-topic-1-gruntwork-landing-zone-architecture.md) +- [Cloud Operating Model: Key Strategies and Best Practices](sources/cloud-operating-model-key-strategies-and-best-practices.md) +- [使用Claude自动生成N8N工作流的实操教程](sources/使用claude自动生成n8n工作流的实操教程.md) +- [万字讲透OpenClaw Workspace深度解析](sources/万字讲透openclaw-workspace深度解析-2026-03-21.md) +- [万字保姆级教程，让你90天跑通一人公司模式（附AI提示词）](sources/万字保姆级教程-90天跑通一人公司模式-2026-03-29.md) +- [YouTube Content Pipeline](sources/youtube-content-pipeline.md) +- [X/Twitter Automation from Chat](sources/x-twitter-automation.md) +- [X Account Analysis](sources/x-account-analysis.md) +- [Todoist Task Manager](sources/todoist-task-manager.md) +- [Semantic Memory Search](sources/semantic-memory-search.md) +- [Self-Healing Home Server & Infrastructure Management](sources/self-healing-home-server.md) +- [Second Brain](sources/second-brain.md) +- [Project State Management System: Event-Driven Alternative to Kanban](sources/project-state-management.md) +- [Pre-Build Idea Validator](sources/pre-build-idea-validator.md) +- [Polymarket Autopilot](sources/polymarket-autopilot.md) +- [Podcast Production Pipeline](sources/podcast-production-pipeline.md) +- [Phone Call Notifications](sources/phone-call-notifications.md) +- [Phone-Based Personal Assistant](sources/phone-based-personal-assistant.md) +- [Personal CRM with Automatic Contact Discovery](sources/personal-crm.md) +- [Goal-Driven Autonomous Tasks](sources/overnight-mini-app-builder.md) +- [OpenClaw + n8n Workflow Orchestration](sources/n8n-workflow-orchestration.md) +- [Multi-Source Tech News Digest](sources/multi-source-tech-news-digest.md) +- [Multi-Channel AI Customer Service Platform](sources/multi-channel-customer-service.md) +- [Multi-Channel Personal Assistant](sources/multi-channel-assistant.md) +- [Multi-Agent Specialized Team (Solo Founder Setup)](sources/multi-agent-team.md) +- [Automated Meeting Notes & Action Items](sources/meeting-notes-action-items.md) +- [Market Research & Product Factory](sources/market-research-product-factory.md) +- [Local CRM Framework with DenchClaw](sources/local-crm-framework.md) +- [LaTeX Paper Writing](sources/latex-paper-writing.md) +- [Personal Knowledge Base (RAG)](sources/knowledge-base-rag.md) +- [Inbox De-clutter](sources/inbox-declutter.md) +- [Health & Symptom Tracker](sources/health-symptom-tracker.md) +- [Habit Tracker & Accountability Coach](sources/habit-tracker-accountability-coach.md) +- [Family Calendar Aggregation & Household Assistant](sources/family-calendar-household-assistant.md) +- [Event Guest Confirmation](sources/event-guest-confirmation.md) +- [AI-Powered Earnings Tracker](sources/earnings-tracker.md) +- [Dynamic Dashboard with Sub-agent Spawning](sources/dynamic-dashboard.md) +- [Daily YouTube Digest](sources/daily-youtube-digest.md) +- [Daily Reddit Digest](sources/daily-reddit-digest.md) +- [Custom Morning Brief](sources/custom-morning-brief.md) +- [Multi-Agent Content Factory](sources/content-factory.md) +- [Autonomous Project Management with Subagents](sources/autonomous-project-management.md) +- [Autonomous Educational Game Development Pipeline](sources/autonomous-game-dev-pipeline.md) +- [arXiv Paper Reader](sources/arxiv-paper-reader.md) +- [OpenClaw as Desktop Cowork (AionUi) — Remote Rescue & Multi-Agent Hub](sources/aionui-cowork-desktop.md) +- [n8n调用hermes-agents的工作流架构](sources/n8n调用hermes-agents的工作流架构.md) — (expected: wiki/sources/n8n调用hermes-agents的工作流架构.md — source missing) +- [n8n + Claude：通过自然语言自动化工作流](sources/n8n-claude-通过自然语言自动化工作流.md) +- [n8n-调用openclaw-agents的工作流架构](sources/n8n-调用openclaw-agents的工作流架构.md) — (expected: wiki/sources/n8n-调用openclaw-agents的工作流架构.md — source missing) +- [N8N Full Tutorial Building AI Agents in 2025 for Beginners!](sources/n8n-full-tutorial-building-ai-agents-in-2025-for-beginners.md) +- [n8n Docker 安装与更新](sources/n8n-docker-install-update.md) +- [n8n configure telegram trigger](sources/n8n-configure-telegram-trigger.md) +- [Claude Code 调用方法总结](sources/claude-code调用方法总结.md) +- [Workflow Optimizer Agent Personality](sources/testing-workflow-optimizer.md) +- [Tool Evaluator Agent Personality](sources/testing-tool-evaluator.md) +- [Test Results Analyzer Agent Personality](sources/testing-test-results-analyzer.md) +- [Testing Reality Checker](sources/testing-reality-checker.md) +- [Performance Benchmarker Agent Personality](sources/testing-performance-benchmarker.md) +- [Testing Evidence Collector Agent Personality](sources/testing-evidence-collector.md) +- [API Tester Agent Personality](sources/testing-api-tester.md) +- [Accessibility Auditor Agent Personality](sources/testing-accessibility-auditor.md) +- [Support Responder Agent Personality](sources/support-support-responder.md) +- [Support Legal Compliance Checker Agent Personality](sources/support-legal-compliance-checker.md) +- [Support Infrastructure Maintainer Agent Personality](sources/support-infrastructure-maintainer.md) +- [Finance Tracker Agent Personality](sources/support-finance-tracker.md) +- [Executive Summary Generator Agent Personality](sources/support-executive-summary-generator.md) +- [Analytics Reporter Agent Personality](sources/support-analytics-reporter.md) - [scenario-startup-mvp](sources/scenario-startup-mvp.md) — (expected: wiki/sources/scenario-startup-mvp.md — source missing) - [scenario-marketing-campaign](sources/scenario-marketing-campaign.md) — (expected: wiki/sources/scenario-marketing-campaign.md — source missing) - [scenario-incident-response](sources/scenario-incident-response.md) — (expected: wiki/sources/scenario-incident-response.md — source missing) @@ -508,14 +288,167 @@ - [agent-activation-prompts](sources/agent-activation-prompts.md) — (expected: wiki/sources/agent-activation-prompts.md — source missing) - [quickstart](sources/quickstart.md) — (expected: wiki/sources/quickstart.md — source missing) - [executive-brief](sources/executive-brief.md) — (expected: wiki/sources/executive-brief.md — source missing) +- [ZK Steward Agent](sources/zk-steward.md) +- [Supply Chain Strategist Agent](sources/supply-chain-strategist.md) +- [Study Abroad Advisor](sources/study-abroad-advisor.md) +- [Workflow Architect Agent Personality](sources/specialized-workflow-architect.md) +- [Specialized Salesforce Architect](sources/specialized-salesforce-architect.md) +- [Model QA Specialist](sources/specialized-model-qa.md) +- [MCP Builder Agent](sources/specialized-mcp-builder.md) +- [Korean Business Navigator](sources/specialized-korean-business-navigator.md) +- [French Consulting Market Navigator](sources/specialized-french-consulting-market.md) +- [Document Generator Agent](sources/specialized-document-generator.md) +- [Specialized Developer Advocate](sources/specialized-developer-advocate.md) +- [Cultural Intelligence Strategist](sources/specialized-cultural-intelligence-strategist.md) +- [Specialized Civil Engineer Agent](sources/specialized-civil-engineer.md) +- [specialized-chief-of-staff](sources/specialized-chief-of-staff.md) — (expected: wiki/sources/specialized-chief-of-staff.md — source missing) +- [sales-outreach](sources/sales-outreach.md) — (expected: wiki/sources/sales-outreach.md — source missing) +- [Sales Data Extraction Agent](sources/sales-data-extraction-agent.md) +- [retail-customer-returns](sources/retail-customer-returns.md) — (expected: wiki/sources/retail-customer-returns.md — source missing) +- [Report Distribution Agent](sources/report-distribution-agent.md) +- [Recruitment Specialist Agent](sources/recruitment-specialist.md) +- [real-estate-buyer-seller](sources/real-estate-buyer-seller.md) — (expected: wiki/sources/real-estate-buyer-seller.md — source missing) +- [LSP/Index Engineer Agent Personality](sources/lsp-index-engineer.md) +- [loan-officer-assistant](sources/loan-officer-assistant.md) — (expected: wiki/sources/loan-officer-assistant.md — source missing) +- [legal-document-review](sources/legal-document-review.md) — (expected: wiki/sources/legal-document-review.md — source missing) +- [legal-client-intake](sources/legal-client-intake.md) — (expected: wiki/sources/legal-client-intake.md — source missing) +- [legal-billing-time-tracking](sources/legal-billing-time-tracking.md) — (expected: wiki/sources/legal-billing-time-tracking.md — source missing) +- [language-translator](sources/language-translator.md) — (expected: wiki/sources/language-translator.md — source missing) +- [Identity Graph Operator](sources/identity-graph-operator.md) +- [hr-onboarding](sources/hr-onboarding.md) — (expected: wiki/sources/hr-onboarding.md — source missing) +- [hospitality-guest-services](sources/hospitality-guest-services.md) — (expected: wiki/sources/hospitality-guest-services.md — source missing) +- [Healthcare Marketing Compliance Specialist](sources/healthcare-marketing-compliance.md) +- [healthcare-customer-service](sources/healthcare-customer-service.md) — (expected: wiki/sources/healthcare-customer-service.md — source missing) +- [Government Digital Presales Consultant](sources/government-digital-presales-consultant.md) +- [Data Consolidation Agent](sources/data-consolidation-agent.md) +- [customer-service](sources/customer-service.md) — (expected: wiki/sources/customer-service.md — source missing) +- [Corporate Training Designer](sources/corporate-training-designer.md) +- [Compliance Auditor Agent](sources/compliance-auditor.md) +- [Blockchain Security Auditor](sources/blockchain-security-auditor.md) +- [Automation Governance Architect](sources/automation-governance-architect.md) +- [Agents Orchestrator](sources/agents-orchestrator.md) +- [Agentic Identity & Trust Architect](sources/agentic-identity-trust.md) +- [Accounts Payable Agent Personality](sources/accounts-payable-agent.md) +- [XR Interface Architect Agent Personality](sources/xr-interface-architect.md) +- [XR Immersive Developer Agent Personality](sources/xr-immersive-developer.md) +- [XR Cockpit Interaction Specialist Agent](sources/xr-cockpit-interaction-specialist.md) +- [visionOS Spatial Engineer](sources/visionos-spatial-engineer.md) +- [Terminal Integration Specialist](sources/terminal-integration-specialist.md) +- [macOS Spatial/Metal Engineer Agent Personality](sources/macos-spatial-metal-engineer.md) +- [OpenCode Integration](sources/readme.md) +- [Sales Proposal Strategist](sources/sales-proposal-strategist.md) +- [Pipeline Analyst Agent](sources/sales-pipeline-analyst.md) +- [Outbound Strategist Agent](sources/sales-outbound-strategist.md) +- [Sales Engineer Agent](sources/sales-engineer.md) +- [Discovery Coach Agent](sources/sales-discovery-coach.md) +- [Deal Strategist Agent](sources/sales-deal-strategist.md) +- [Sales Coach Agent](sources/sales-coach.md) +- [Account Strategist Agent](sources/sales-account-strategist.md) +- [Senior Project Manager Agent Personality](sources/project-manager-senior.md) +- [Studio Producer Agent Personality](sources/project-management-studio-producer.md) +- [Studio Operations Agent Personality](sources/project-management-studio-operations.md) +- [Project Shepherd Agent Personality](sources/project-management-project-shepherd.md) +- [Jira Workflow Steward Agent Personality](sources/project-management-jira-workflow-steward.md) +- [Experiment Tracker Agent Personality](sources/project-management-experiment-tracker.md) +- [Product Trend Researcher Agent](sources/product-trend-researcher.md) +- [Product Sprint Prioritizer Agent](sources/product-sprint-prioritizer.md) +- [Product Manager Agent](sources/product-manager.md) +- [Product Feedback Synthesizer Agent](sources/product-feedback-synthesizer.md) +- [Behavioral Nudge Engine](sources/product-behavioral-nudge-engine.md) +- [Paid Media Tracking & Measurement Specialist Agent](sources/paid-media-tracking-specialist.md) +- [Paid Media Search Query Analyst Agent](sources/paid-media-search-query-analyst.md) +- [Paid Media Programmatic & Display Buyer Agent](sources/paid-media-programmatic-buyer.md) +- [Paid Media PPC Campaign Strategist Agent](sources/paid-media-ppc-strategist.md) +- [Paid Social Strategist](sources/paid-media-paid-social-strategist.md) +- [Paid Media Ad Creative Strategist Agent](sources/paid-media-creative-strategist.md) +- [Paid Media Auditor Agent](sources/paid-media-auditor.md) +- [Marketing Zhihu Strategist](sources/marketing-zhihu-strategist.md) +- [Marketing Xiaohongshu Specialist](sources/marketing-xiaohongshu-specialist.md) +- [Marketing Weibo Strategist](sources/marketing-weibo-strategist.md) +- [Marketing WeChat Official Account Manager](sources/marketing-wechat-official-account.md) +- [Marketing Video Optimization Specialist](sources/marketing-video-optimization-specialist.md) +- [Marketing Twitter Engager](sources/marketing-twitter-engager.md) +- [Marketing TikTok Strategist](sources/marketing-tiktok-strategist.md) +- [Social Media Strategist](sources/marketing-social-media-strategist.md) +- [Marketing Short-Video Editing Coach](sources/marketing-short-video-editing-coach.md) +- [Marketing SEO Specialist](sources/marketing-seo-specialist.md) +- [Marketing Reddit Community Builder](sources/marketing-reddit-community-builder.md) +- [Marketing Private Domain Operator](sources/marketing-private-domain-operator.md) +- [Marketing Podcast Strategist](sources/marketing-podcast-strategist.md) +- [Marketing Livestream Commerce Coach](sources/marketing-livestream-commerce-coach.md) +- [LinkedIn Content Creator](sources/marketing-linkedin-content-creator.md) +- [Marketing Kuaishou Strategist](sources/marketing-kuaishou-strategist.md) +- [Marketing Instagram Curator](sources/marketing-instagram-curator.md) +- [Marketing Growth Hacker Agent](sources/marketing-growth-hacker.md) +- [Marketing Douyin Strategist](sources/marketing-douyin-strategist.md) +- [Marketing Cross-Border E-Commerce Specialist](sources/marketing-cross-border-ecommerce.md) +- [Marketing Content Creator](sources/marketing-content-creator.md) +- [China Market Localization Strategist](sources/marketing-china-market-localization-strategist.md) +- [Marketing China E-Commerce Operator](sources/marketing-china-ecommerce-operator.md) +- [Marketing Carousel Growth Engine](sources/marketing-carousel-growth-engine.md) +- [Book Co-Author](sources/marketing-book-co-author.md) +- [Marketing Bilibili Content Strategist](sources/marketing-bilibili-content-strategist.md) +- [Marketing Baidu SEO Specialist](sources/marketing-baidu-seo-specialist.md) +- [App Store Optimizer](sources/marketing-app-store-optimizer.md) +- [AI Citation Strategist](sources/marketing-ai-citation-strategist.md) +- [marketing-agentic-search-optimizer](sources/marketing-agentic-search-optimizer.md) — (expected: wiki/sources/marketing-agentic-search-optimizer.md — source missing) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [Backend Architect with Memory](sources/backend-architect-with-memory.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [OpenCode Integration](sources/readme.md) +- [Unreal World Builder Agent Personality](sources/unreal-world-builder.md) +- [Unreal Technical Artist](sources/unreal-technical-artist.md) +- [Unreal Systems Engineer](sources/unreal-systems-engineer.md) +- [Unreal Multiplayer Architect](sources/unreal-multiplayer-architect.md) +- [Unity Shader Graph Artist](sources/unity-shader-graph-artist.md) +- [Unity Multiplayer Engineer](sources/unity-multiplayer-engineer.md) +- [Unity Editor Tool Developer](sources/unity-editor-tool-developer.md) +- [Unity Architect](sources/unity-architect.md) +- [Technical Artist](sources/technical-artist.md) +- [Roblox Systems Scripter Agent Personality](sources/roblox-systems-scripter.md) +- [Roblox Experience Designer](sources/roblox-experience-designer.md) +- [Roblox Avatar Creator Agent Personality](sources/roblox-avatar-creator.md) +- [Narrative Designer Agent Personality](sources/narrative-designer.md) +- [Level Designer Agent Personality](sources/level-designer.md) +- [Godot Shader Developer Agent Personality](sources/godot-shader-developer.md) +- [Godot Multiplayer Engineer Agent Personality](sources/godot-multiplayer-engineer.md) +- [Godot Gameplay Scripter Agent Personality](sources/godot-gameplay-scripter.md) +- [Game Designer Agent Personality](sources/game-designer.md) +- [Game Audio Engineer Agent](sources/game-audio-engineer.md) +- [Blender Add-on Engineer Agent Personality](sources/blender-addon-engineer.md) +- [finance-tax-strategist](sources/finance-tax-strategist.md) — (expected: wiki/sources/finance-tax-strategist.md — source missing) +- [finance-investment-researcher](sources/finance-investment-researcher.md) — (expected: wiki/sources/finance-investment-researcher.md — source missing) +- [finance-fpa-analyst](sources/finance-fpa-analyst.md) — (expected: wiki/sources/finance-fpa-analyst.md — source missing) +- [finance-financial-analyst](sources/finance-financial-analyst.md) — (expected: wiki/sources/finance-financial-analyst.md — source missing) +- [finance-bookkeeper-controller](sources/finance-bookkeeper-controller.md) — (expected: wiki/sources/finance-bookkeeper-controller.md — source missing) +- [Multi-Agent Workflow: Startup MVP with Persistent Memory](sources/workflow-with-memory.md) +- [Multi-Agent Workflow: Startup MVP](sources/workflow-startup-mvp.md) +- [Multi-Agent Workflow: Landing Page Sprint](sources/workflow-landing-page.md) +- [Workflow Example: Book Chapter Development](sources/workflow-book-chapter.md) +- [Nexus Spatial: Full Agency Discovery Exercise](sources/nexus-spatial-discovery.md) +- [OpenCode Integration](sources/readme.md) - [engineering-wechat-mini-program-developer](sources/engineering-wechat-mini-program-developer.md) — (expected: wiki/sources/engineering-wechat-mini-program-developer.md — source missing) +- [engineering-voice-ai-integration-engineer](sources/engineering-voice-ai-integration-engineer.md) — (expected: wiki/sources/engineering-voice-ai-integration-engineer.md — source missing) - [engineering-threat-detection-engineer](sources/engineering-threat-detection-engineer.md) — (expected: wiki/sources/engineering-threat-detection-engineer.md — source missing) - [engineering-technical-writer](sources/engineering-technical-writer.md) — (expected: wiki/sources/engineering-technical-writer.md — source missing) - [engineering-sre](sources/engineering-sre.md) — (expected: wiki/sources/engineering-sre.md — source missing) - [engineering-solidity-smart-contract-engineer](sources/engineering-solidity-smart-contract-engineer.md) — (expected: wiki/sources/engineering-solidity-smart-contract-engineer.md — source missing) +- [Software Architect Agent Personality](sources/engineering-software-architect.md) - [engineering-senior-developer](sources/engineering-senior-developer.md) — (expected: wiki/sources/engineering-senior-developer.md — source missing) - [engineering-security-engineer](sources/engineering-security-engineer.md) — (expected: wiki/sources/engineering-security-engineer.md — source missing) - [engineering-rapid-prototyper](sources/engineering-rapid-prototyper.md) — (expected: wiki/sources/engineering-rapid-prototyper.md — source missing) +- [Mobile App Builder Agent Personality](sources/engineering-mobile-app-builder.md) +- [engineering-minimal-change-engineer](sources/engineering-minimal-change-engineer.md) — (expected: wiki/sources/engineering-minimal-change-engineer.md — source missing) - [engineering-incident-response-commander](sources/engineering-incident-response-commander.md) — (expected: wiki/sources/engineering-incident-response-commander.md — source missing) - [engineering-git-workflow-master](sources/engineering-git-workflow-master.md) — (expected: wiki/sources/engineering-git-workflow-master.md — source missing) - [engineering-frontend-developer](sources/engineering-frontend-developer.md) — (expected: wiki/sources/engineering-frontend-developer.md — source missing) @@ -526,11 +459,79 @@ - [engineering-devops-automator](sources/engineering-devops-automator.md) — (expected: wiki/sources/engineering-devops-automator.md — source missing) - [engineering-database-optimizer](sources/engineering-database-optimizer.md) — (expected: wiki/sources/engineering-database-optimizer.md — source missing) - [engineering-data-engineer](sources/engineering-data-engineer.md) — (expected: wiki/sources/engineering-data-engineer.md — source missing) +- [engineering-codebase-onboarding-engineer](sources/engineering-codebase-onboarding-engineer.md) — (expected: wiki/sources/engineering-codebase-onboarding-engineer.md — source missing) - [engineering-code-reviewer](sources/engineering-code-reviewer.md) — (expected: wiki/sources/engineering-code-reviewer.md — source missing) - [engineering-cms-developer](sources/engineering-cms-developer.md) — (expected: wiki/sources/engineering-cms-developer.md — source missing) -- [engineering-backend-architect](sources/engineering-backend-architect.md) — (expected: wiki/sources/engineering-backend-architect.md — source missing) +- [Autonomous Optimization Architect](sources/engineering-autonomous-optimization-architect.md) - [engineering-ai-engineer](sources/engineering-ai-engineer.md) — (expected: wiki/sources/engineering-ai-engineer.md — source missing) - [engineering-ai-data-remediation-engineer](sources/engineering-ai-data-remediation-engineer.md) — (expected: wiki/sources/engineering-ai-data-remediation-engineer.md — source missing) +- [Design Whimsy Injector](sources/design-whimsy-injector.md) +- [Visual Storyteller Agent](sources/design-visual-storyteller.md) +- [UX Researcher Agent Personality](sources/design-ux-researcher.md) +- [ArchitectUX Agent Personality](sources/design-ux-architect.md) +- [UI Designer Agent Personality](sources/design-ui-designer.md) +- [Inclusive Visuals Specialist](sources/design-inclusive-visuals-specialist.md) +- [Image Prompt Engineer Agent](sources/design-image-prompt-engineer.md) +- [Design Brand Guardian](sources/design-brand-guardian.md) +- [Academic Psychologist](sources/academic-psychologist.md) +- [Academic Narratologist](sources/academic-narratologist.md) +- [Historian Agent Personality](sources/academic-historian.md) +- [Academic Geographer](sources/academic-geographer.md) +- [Academic Anthropologist](sources/academic-anthropologist.md) +- [security](sources/security.md) — (expected: wiki/sources/security.md — source missing) +- [为 The Agency 贡献代码](sources/contributing_zh-cn.md) +- [Contributing to The Agency](sources/contributing.md) +- [Your-AI-Isn-t-Stupid---It-Just-Needs-a-Better-Harness--Lychee-Technology-Engineering-Blog](sources/Your-AI-Isn-t-Stupid---It-Just-Needs-a-Better-Harness--Lychee-Technology-Engineering-Blog.md) — (expected: wiki/sources/Your-AI-Isn-t-Stupid---It-Just-Needs-a-Better-Harness--Lychee-Technology-Engineering-Blog.md — source missing) +- [open-webui-hermes-agent](sources/open-webui-hermes-agent.md) — (expected: wiki/sources/open-webui-hermes-agent.md — source missing) +- [MCP在Cursor中的集成与应用详解](sources/mcp在cursor中的集成与应用详解.md) +- [llm-wiki](sources/llm-wiki.md) — (expected: wiki/sources/llm-wiki.md — source missing) +- [karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环](sources/karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环.md) — (expected: wiki/sources/karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环.md — source missing) +- [Google 5个 Agent Skill 设计模式](sources/google-5个agent-skill设计模式-2026-03-19.md) +- [Expose-hermes-agent-as-an-OpenAI-compatible-API-for-any-frontend](sources/Expose-hermes-agent-as-an-OpenAI-compatible-API-for-any-frontend.md) — (expected: wiki/sources/Expose-hermes-agent-as-an-OpenAI-compatible-API-for-any-frontend.md — source missing) +- [I Went Through Every AI Memory Tool I Could Find. There Are Two Camps.](sources/ai-memory-tools-two-camps.md) +- [谷歌深夜甩出一份【Nano Banana Pro提示词指南】，手把手教你生产专业级内容，实战案例+提示词模版](sources/谷歌深夜甩出一份-nano-banana-pro提示词指南-手把手教你生产专业级内容-实战案例-提示词模版.md) +- [详细！离线部署大模型：ollama+deepseek+open-webui安装使用方法及常见问题解决 1](sources/详细-离线部署大模型-ollama-deepseek-open-webui安装使用方法及常见问题解决-1.md) +- [系统提示词构建原则](sources/系统提示词构建原则.md) +- [清华出的DeepSeek使用手册，104页，真的是太厉害了！（免费领取）](sources/清华出的deepseek使用手册-104页-真的是太厉害了-免费领取.md) +- [文字生成视频网站推荐](sources/文字生成视频网站推荐.md) +- [教學 ChatGPT 先做知識整理，再讓 Canva、 Gamma AI 輸出簡報](sources/教學-chatgpt-先做知識整理-再讓-canva-gamma-ai-輸出簡報.md) +- [我的工具集](sources/我的工具集.md) +- [我用 Gemini 3 一口气做了 10 个应用，附教程](sources/我用-gemini-3-一口气做了-10-个应用-附教程.md) +- [如何让ai生成风格一致的图片](sources/如何让ai生成风格一致的图片.md) — (expected: wiki/sources/如何让ai生成风格一致的图片.md — source missing) +- [如何利用Sora接口实现视频自动化生成工作流](sources/如何利用sora接口实现视频自动化生成工作流.md) +- [如何写出完美的Prompt（提示词）？](sources/如何写出完美的prompt-提示词.md) +- [大模型相关术语和框架总结｜LLM、MCP、Prompt、RAG、vLLM、Token、数据蒸馏](sources/大模型相关术语和框架总结｜llm-mcp-prompt-rag-vllm-token-数据蒸馏.md) +- [在 Ubuntu 安装 Ollama 并运行 Qwen2.5‑Coder 7B](sources/在-ubuntu-安装-ollama-并运行-qwen2-5‑coder-7b.md) +- [固定镜头短视频制作的AI全流程解析](sources/固定镜头短视频制作的ai全流程解析.md) +- [全网最全！Nano Banana 2 使用指南（2025年12月更新）](sources/全网最全-nano-banana-2-使用指南-2025年12月更新-1.md) +- [二创视频必不可少！2025年最热门AI工具推荐合集-AI配音、声音克隆](sources/二创视频必不可少-2025年最热门ai工具推荐合集-ai配音-声音克隆.md) +- [不会Gemini的产品经理真的要被淘汰了 | 附保姆级PRD生成指南](sources/不会gemini的产品经理真的要被淘汰了-附保姆级prd生成指南.md) +- [一语点醒梦中人](sources/一语点醒梦中人.md) +- [codecrafters-io/build-your-own-x: Master programming by recreating your favorite technologies from scratch](sources/codecrafters-iobuild-your-own-x-master-programming-by-recreating-your-favorite-technologies-from-scratch.md) +- [Claude Prompt Library 汇总表](sources/useful-prompt-lib.md) +- [The Picture They Paint of You](sources/the-picture-they-paint-of-you.md) +- [RAG从入门到精通系列1：基础RAG](sources/rag从入门到精通系列1-基础rag.md) +- [OpenAI ChatGPT 个性化定义](sources/openai-chatgpt-个性化定义.md) +- [Never write another prompt](sources/never-write-another-prompt.md) +- [Nano Banana Pro 提示词指南与策略（上篇）](sources/nano-banana-pro-prompting-guide-strategies-1.md) +- [Nano Banana 提示词框架](sources/nano-banana-提示词框架.md) +- [Multi-Agent System Reliability](sources/multi-agent-system-reliability.md) +- [Learn AI for free directly from top companies](sources/learn-ai-for-free-directly-from-top-companies.md) +- [LLMs、RAG、AI Agent 三个到底什么区别？](sources/llms-rag-ai-agent-三个到底什么区别.md) +- [If You Have Multiple Interests, Do Not Waste the Next 2-3 Years](sources/if-you-have-multiple-interests-do-not-waste-the-next-2-3-years-如果你有多项兴趣爱好-不要浪费接下来的两三年时间.md) +- [How to Get the RSS Feed For Any YouTube Channel](sources/how-to-get-the-rss-feed-for-any-youtube-channel.md) +- [Google 神级生产力工具，所有 GitHub 开源平替都找到了。](sources/google-神级生产力工具-所有-github-开源平替都找到了.md) +- [GitHub 上 5000 人收藏的 Vibe Coding 神级指南](sources/github-上-5000-人收藏的-vibe-coding-神级指南.md) +- [Designing for Agentic AI](sources/designing-for-agentic-ai.md) +- [Best 7 news API data feeds - AI News](sources/best-7-news-api-data-feeds-ai-news.md) +- [AI 解决方案专家培训课程](sources/ai-解决方案专家培训课程.md) +- [A Formalization of Recursive Self-Optimizing Generative Systems](sources/a-formalization-of-recursive-self-optimizing-generative-systems.md) +- [7 ways I use NotebookLM to make my life easier](sources/7-ways-i-use-notebooklm-to-make-my-life-easier.md) +- [3.2 万人收藏的 Claude Skills，才是 AI 这条路上最值得研究的一套范式！](sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式.md) +- [3.2 万人收藏的 Claude Skills，才是 AI 这条路上最值得研究的一套范式！](sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式-1.md) +- [2025 年 11 个神级 AI 开源平替，GitHub 杀疯了](sources/2025-年-11-个神级-ai-开源平替-github-杀疯了.md) +- [14个免费的AI图生视频工具，用AI让图片动起来](sources/14个免费的ai图生视频工具-用ai让图片动起来-ai视频教程-ai自动化工作流定制服务-ai培训学习平台-黑喵大叔.md) +- [engineering-backend-architect](sources/engineering-backend-architect.md) — (expected: wiki/sources/engineering-backend-architect.md — source missing) ## Entities - [Acemoglu](entities/Acemoglu.md) @@ -980,6 +981,7 @@ - [Claudian](concepts/Claudian.md) - [ClientPrediction](concepts/ClientPrediction.md) - [Cloud-Adoption-Strategy](concepts/Cloud-Adoption-Strategy.md) +- [Cloud-Computing](concepts/Cloud-Computing.md) - [Cloud-Cost-Optimization](concepts/Cloud-Cost-Optimization.md) - [Cloud-DevOps-Maturity-Model](concepts/Cloud-DevOps-Maturity-Model.md) - [Cloud-Governance](concepts/Cloud-Governance.md) @@ -1066,6 +1068,7 @@ - [Design-Thinking](concepts/Design-Thinking.md) - [Design-to-Code-Workflow](concepts/Design-to-Code-Workflow.md) - [DevOps-Maturity](concepts/DevOps-Maturity.md) +- [DevOps-Maturity-Model](concepts/DevOps-Maturity-Model.md) - [DevOpsCulture](concepts/DevOpsCulture.md) - [DevSecOps](concepts/DevSecOps.md) - [Dialogue-Writing-Standards](concepts/Dialogue-Writing-Standards.md) @@ -1291,6 +1294,7 @@ - [Multi-factor-Authentication](concepts/Multi-factor-Authentication.md) - [Multi-Tenancy](concepts/Multi-Tenancy.md) - [Multi-Window-Architecture](concepts/Multi-Window-Architecture.md) +- [MVP](concepts/MVP.md) - [N8nWorkflowStandard](concepts/N8nWorkflowStandard.md) - [Nanite](concepts/Nanite.md) - [Narrative-Debt](concepts/Narrative-Debt.md) diff --git a/wiki/log.md b/wiki/log.md index 01a46a49..2e13bc82 100644 --- a/wiki/log.md +++ b/wiki/log.md @@ -1,4 +1,57 @@ -## [2026-04-26] ingest | Autonomous Optimization Architect Agent Personality +## [2026-04-26] ingest | DevOps Maturity Model From Traditional IT to Advanced DevOps +- Source file: Cloud & DevOps/DevOps Maturity Model From Traditional IT to Advanced DevOps.md +- Status: ✅ 成功摄入 +- Summary: DevOps 成熟度模型五阶段演进框架——从传统 IT（Phase 1 瀑布式/团队孤立）到完全成熟（Phase 5 连续部署/零人工干预）；四个核心评估维度：文化与战略、自动化、结构与流程、协作与共享、技术；衡量指标：DORA 四项 + 错误预算 + 时间到市场；DevSecOps 集成安全于每个阶段；七类常见演进障碍识别。 +- Concepts created: [[concepts/Error-Budget]]、[[concepts/Immutable-Infrastructure]]、[[concepts/MVP]]（Error Budget 和 Immutable Infrastructure 原有页面已存在但未关联本文档，已更新 sources 字段；MVP 新建） +- Entities created: 无（DevOps Maturity Model Entity 页面已存在，已追加本文档为来源） +- Source page: wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md +- Notes: index.md Sources 部分更新原有无日期条目为 [2025-03-01]；概念页面更新：[[entities/DevOps-Maturity-Model]] 已追加摄取记录，[[concepts/Error-Budget]] 和 [[concepts/Immutable-Infrastructure]] 已添加 sources 引用；[[concepts/MVP]] 新建并添加到 index.md；冲突检测：与 [[DevOps Culture and Transformation]] 存在文化转型是"前提还是结果"的潜在视角差异；与 Waterfall 的对比无实质性冲突。 + +## [2026-04-28] ingest | RTO vs RPO: Key Differences for Modern Disaster Recovery +- Source file: Cloud & DevOps/RTO vs RPO Key Differences for Modern Disaster Recovery.md +- Status: ✅ 成功摄入 +- Summary: RTO（恢复时间目标）与 RPO（恢复点目标）的核心区别与在现代持续交付中的实践——RTO 衡量停机时长容忍度，RPO 衡量数据丢失容忍度；现代部署场景下软件故障（Bug/错误迁移/AI 模型异常）比硬件灾难更频繁；Feature Flag 通过部署与发布解耦、渐进式灰度发布（1%→5%→25%→100%）、Kill Switch 将 RTO 从"小时级回滚"缩短至"秒级开关切换"；应用分层策略（Tier 1 Critical <5min/<1min → Tier 3 <4h/<1h）；成本效益原则——预防优于恢复，Feature Flag 方案比传统热备基础设施成本更低。 +- Concepts created: FeatureFlag/RTO/RPO/KillSwitch/ProgressiveRollout/MicroRecovery（以上6个概念均仅在本文档出现1次，未达≥2次独立建页阈值，保留于 Source Page 内嵌引用） +- Entities created: LaunchDarkly/Veeam/Acronis/HP/ChristianDior（以上5个实体均仅在本文档出现1次，未达≥2次独立建页阈值，保留于 Source Page 内嵌引用） +- Source page: wiki/sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md +- Notes: index.md Sources 部分更新原无日期条目，添加 [2019-01-18] 日期戳和一行摘要；overview.md Cloud Transformation & DevOps 部分新增 entry，置于 [[ctp-topic-72-enterprise-dr-strategy-aws-backup]] 之后，强调软件层 DR（Feature Flag/秒级 RTO）与基础设施层 DR（AWS Backup/热备）的互补关系；冲突检测：与 [[ctp-topic-72-enterprise-dr-strategy-aws-backup]] 和 [[what-i-know-about-cloud-service-delivery-1]]（第12领域"备份恢复与灾难管理"）形成引用关系，无实质冲突；与传统 DevOps DR 认知（硬件灾难为主）存在框架视角差异（现代：软件故障更频繁），属互补而非冲突。 + + +- Source file: Cloud & DevOps/How Can a Multi Cloud Strategy Transform Your Business ROI.md +- Status: ✅ 成功摄入 +- Summary: 多云策略（Multi-Cloud Strategy）商业价值——78% 企业使用 3+ 公有云；86% 企业计划 2024 年底采用多云；优化后 30% 运营成本降低（Forrester）；8 大商业价值：避免锁定/增强弹性/提升安全/弹性扩展/成本优化/加速创新/满足合规/性能优化；行业案例：电商/医疗/金融；实施路径：评估→选择提供商→集成管理→监控优化 +- Concepts created: 无（Multi-Cloud-Strategy/Vendor-Lock-In/Data-Sovereignty/High-Availability/Scalability/Cost-Optimization 已在 Wiki 中存在对应 Entity/Concept 页面，未达新建阈值） +- Entities created: 无（Bacancy Technology 仅出现 1 次，未达 ≥2 次独立建页阈值） +- Source page: wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md +- Notes: index.md Sources 部分更新原有多云来源条目，添加 [2026-04-27] 日期戳；overview.md Cloud Transformation & DevOps 部分新增本 Source entry，补充多云 ROI 量化数据（78%/86%/30%）和实施框架，与 [[cloud-operating-model-key-strategies-and-best-practices]] 形成互补（多云=选择层，Cloud Operating Model=治理层）；冲突检测：与 [[cloud-operating-model-key-strategies-and-best-practices]] 中的"统一云治理"存在潜在张力——两者互补而非冲突；与现有 [[Multi-Cloud-Strategy]] 概念页面一致，无冲突。 + +## [2026-04-26] ingest | What I Know About Cloud Service Delivery 1 +- Source file: Cloud & DevOps/What I know about Cloud Service Delivery 1.md +- Status: ✅ 成功摄入 +- Summary: 云服务交付（Cloud Service Delivery）完整生命周期管理框架——12 大管理领域：服务供给与部署、基础设施管理、平台管理 PaaS、应用运营管理、安全与合规、性能与可用性监控、事件与问题管理、变更与配置管理（IaC）、成本管理与优化（FinOps）、客户接入与支持、服务治理与生命周期、备份恢复与灾难管理。核心工具：AWS CloudWatch + Grafana、New Relic、WAF、Terraform IaC。属 Cloud DevOps 成熟度在运营管理维度的具体化。 +- Concepts created: 无（Cloud Service Delivery/SLA/SLO/FinOps/IaC/AIOps 各仅在本文档出现 1 次，未达 ≥2 次独立建页阈值，保留于 Source Page 内嵌引用） +- Entities created: 无（AWS CloudWatch/Grafana/New Relic/WAF/OpenText 各仅在本文档出现 1 次，未达 ≥2 次独立建页阈值） +- Source page: wiki/sources/what-i-know-about-cloud-service-delivery-1.md +- Notes: index.md Sources 部分更新原有无日期条目为 [2026-04-26]；overview.md Cloud Transformation & DevOps 部分新增本 Source entry，补充 12 大云服务交付管理领域详细解读，与 [[cloud-devop-maturity-guideline]] 和 [[devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]] 共同构成完整云运营知识体系；冲突检测：与 [[devops-maturity-model-from-traditional-it-to-advanced-devops]] 存在潜在关联（DevOps 文化成熟度 vs 运营管理），暂无实质性冲突。 + +## [2026-04-26] ingest | Cloud DevOp Maturity - Guideline +- Source file: Cloud & DevOps/Cloud DevOp Maturity - Guideline.md +- Status: ✅ 成功摄入 +- Summary: 企业级 SaaS 公司的云 DevOps 成熟度评估框架与提升路径——基于 DORA 四项核心指标（部署频率、变更前置时间、变更失败率、MTTR）和 CMMI 成熟度模型，从自动化（CI/CD、IaC、测试自动化）、协作文化、监控可观测性、安全集成（DevSecOps）四大支柱进行系统评估。 +- Concepts created: 无（DevOpsMaturityModel/DORAMetrics/CI/CDPipeline/InfrastructureAsCode/DevSecOps/MicroservicesArchitecture/Observability 各在本文档和已有 Wiki 页面中均已存在 Entity/Concept 页面，未达新建阈值，保留于 Source Page 内嵌引用） +- Source page: wiki/sources/cloud-devop-maturity-guideline.md +- Notes: index.md Sources 部分新增 cloud-devop-maturity-guideline.md 条目（替换原有无日期条目）；overview.md Cloud Transformation & DevOps 部分新增本 Source 独立 entry，补充 DORA 四项指标量化评估方法、成熟度提升路线（评估→卓越中心→分阶段实施→持续迭代），与 [[devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]] 和 [[devops-maturity-model-from-traditional-it-to-advanced-devops]] 关联；冲突检测：未发现与其他 Wiki 页面的内容冲突。 + +## [2025-03-02] ingest | DevOps Culture and Transformation +- Source file: Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md +- Status: ✅ 成功摄入 +- Summary: DevOps 文化与转型完整指南——四大文化支柱（跨职能协作/自动化/持续改进 Kaizen/客户导向）、Agile 与 DevOps 的共生关系（Scrum/Kanban + CI/CD）、战略转型 playbook（领导层支持→团队赋能→小步试点→克服阻力）、未来趋势（AI/ML 智能自动化/GitOps/Serverless DevOps/边缘计算/DevSecOps）。 +- Concepts created: 无（DevOps Culture/CI-CD-Pipeline/Infrastructure-as-Code/Kaizen/Shift-Left/Value-Stream-Mapping/GitOps/Serverless-DevOps/Agile-DevOps-Integration 各仅在本文档出现 1 次，未达 ≥2 次独立建页阈值，保留于 Source Page 内嵌引用） +- Entities created: 无（Hemant Sawant/Shenwei 各仅出现 1 次，未达 ≥2 次独立建页阈值） +- Source page: wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md +- Notes: index.md 中原有条目日期已更新为 2025-03-02；overview.md Cloud Transformation & DevOps 部分新增本 Source 独立 entry，补充四大文化支柱、战略转型 playbook、无责事后分析等详细解读，与 [[ctp-topic-4-using-agile-to-run-the-cloud-transformation-program]] 和 [[ctp-topic-33-an-introduction-to-gitops]] 共同构成完整 DevOps 知识体系；冲突检测：未发现与其他 Wiki 页面的内容冲突。 + + - Source file: Agent/agency-agents/engineering/engineering-autonomous-optimization-architect.md - Status: ✅ 成功摄入 - Summary: Autonomous Optimization Architect——AI 系统自我进化的"治理者"，在保证系统不会破产或陷入恶意循环的前提下，持续通过影子测试评估和切换 AI 模型。核心理念："Autonomous routing without a circuit breaker is just an expensive bomb." 核心机制：LLM-as-Judge 评分（数学评分标准替代主观评估）、影子流量测试（5% 异步测试新模型）、语义路由（按 Speed+Cost+Accuracy 综合排名选最优 Provider）、熔断器（失败超阈值自动切断并切换兜底方案）、AI FinOps（追踪每个 Provider 的成本与性能历史）。目标：在 99.99% 稳定性下实现 >40% 成本降低。属 The Agency Engineering 部门。 @@ -4046,3 +4099,57 @@ - Concepts created/updated: [[MultiplayerAPI]]、[[Server-Authoritative Model]]、[[RPC（Remote Procedure Call）]]、[[MultiplayerSynchronizer]]、[[MultiplayerSpawner]]、[[ENet]]、[[WebRTC]]、[[Authority Model]]、[[RPC Security Pattern]] - Source page: wiki/sources/godot-multiplayer-engineer.md - Notes: index.md Sources 第3行已存在正确条目；index.md line 507 原有 broken lint marker entry（expected source missing）已移除；Entity 建页判断：Godot 4 和 Nakama 在源文档中仅出现 1-2 次，未达 Entity 建页阈值 ≥2 次，仅在 source page Key Entities 节记录；冲突记录：与 [[unity-multiplayer-engineer]] 在权威模型实现上有差异，已在 source page Contradictions 节记录（Godot 显式 vs Unity 隐式权威模型） + +## [2026-04-27] ingest | Cloud Maturity Model - A Detailed Guide For Cloud Adoption +- Source file: Cloud & DevOps/Cloud Maturity Model A Detailed Guide For Cloud Adoption.md +- Status: ✅ 成功摄入（source page 格式重写，index.md entry 日期补全，overview.md 新增 entry） +- Summary: 系统性介绍 Cloud Maturity Model (CMM) 云成熟度模型——5级成熟度阶段（Level 0–5）覆盖企业云转型完整路径；关键组成要素覆盖业务维度（财务/战略/组织/文化/治理/合规/采购）和技术维度（架构/应用/DevOps/安全/IaaS/PaaS/SaaS/AI/IoT）；三维评估框架（People/Processes/Technology）；7大收益；最佳实践；7种主流云成熟度模型对比。核心理念：CMM 是云转型全面导航仪，Level 5 是目标但往往更具理想性，建议选择性采纳。 +- Concepts created: 无（Cloud Adoption/Cloud Migration/Cloud Governance/Cloud Security/FinOps/Cloud-Native/Cloud Cost Optimization/Multi-Cloud Strategy/Hybrid Cloud/People-Process-Technology/CCoE/GAP Analysis/Cloud Compliance/CAPEX vs OPEX/TCO 各仅在本文档出现 1-2 次，未达 ≥2 次独立建页阈值，均保留于 Source Page 内嵌引用） +- Entities created: 无（Open Alliance for Cloud Adoption 已于 entities/Open-Alliance-for-Cloud-Adoption.md 建页；Cloud Maturity Model 已于 entities/Cloud-Maturity-Model.md 建页；Cloud Native Maturity Model/CSMM/SAMM/AWS CAF/Azure CAF/GCP CAF 仅在本文档出现 1-2 次，未达 ≥2 次阈值） +- Source page: wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md +- Notes: index.md Sources 部分原有 entry（line 209）缺少日期前缀，已补全为 `[2026-04-26]` 并追加一行摘要；overview.md Cloud Transformation & DevOps 部分（line 183 后）新增本 Source 独立 entry，补充 CMM 5级阶段、三维评估框架、7大收益、最佳实践等详细内容，与 [[cloud-devop-maturity-guideline]]（DevOps 交付能力成熟度）和 [[devops-maturity-model-from-traditional-it-to-advanced-devops]] 共同构成完整成熟度知识体系；Entity/Concept 去重：已检查 wiki/entities 和 wiki/concepts 目录，Cloud-Maturity-Model.md、Cloud-Maturity-Levels.md、Cloud-Adoption-Strategy.md、Cloud-Native.md、Cloud-Governance.md、FinOps.md、Multi-Cloud-Strategy.md、Hybrid-Cloud.md、Cloud-Cost-Optimization.md、DevOps-Maturity.md 等页面均已存在，无需新建；冲突检测：与 [[DevOps Maturity Model]] 在"成熟度框架"视角上存在差异——DevOps 聚焦研发交付能力，CMM 聚焦云采用整体成熟度，两者互补非互斥，已在 Source Page Contradictions 部分记录。 + +## [2026-04-14] ingest | How Agentic AI can help for Cloud DevOps +- Source file: Cloud & DevOps/How Agentic AI can help for Cloud DevOps.md +- Status: ✅ 成功摄入 +- Summary: Agentic AI（具备自主决策和任务执行能力的AI系统）通过七大能力增强 Cloud DevOps：① 自主事故检测与解决（Self-Healing + AI-driven RCA + Predictive Maintenance）；② 自动化云部署与配置（AI Release Manager + IaC 智能审查）；③ 智能成本优化（Rightsizing + Spot Instance 优化，夜间切换可降低40%成本）；④ AI驱动的安全与合规（自动扫描 IAM/容器漏洞并实时修复）；⑤ 智能日志分析与可观测性（AI ChatOps）；⑥ 多租户 SaaS 管理（动态供给 + 自动退租）；⑦ AI增强决策支持（What-If Simulation）。 +- Concepts created: [[Agentic AI]]（已存在，仅补充应用场景）、[[Self-Healing Systems]]（已存在，仅补充应用场景）、[[Root Cause Analysis (RCA)]]（已存在）、[[Predictive Maintenance]]（已存在）、[[Deployment Automation]]（已存在）、[[Rightsizing]]（已存在）、[[Automated Security Audit]]（已存在）、[[Multi-Cloud Cost Optimization]]（已存在）、[[AI ChatOps]]（已存在）、[[What-If Simulation]]（已存在） +- Entities created: 无（Kubernetes、Terraform、CloudWatch、IAM、Spot Instances 均已存在于 Wiki） +- Source page: wiki/sources/how-agentic-ai-can-help-for-cloud-devops.md +- Notes: index.md Sources 部分已存在本条目（line 208），包含一行摘要；source page 包含完整的 Source File、Summary（四大维度）、Key Claims（10条，主体+机制+结果格式）、Key Quotes（4条）、Key Concepts（含10个 wikilinks）、Key Entities（含5个产品/平台 wikilinks）、Connections（含11条依赖/扩展关系）、Contradictions（3组冲突）、Metadata（Author/Tags/Related Sources）；冲突检测：① Agentic AI 自动修复 vs 人工审批控制（安全合规要求审批 vs 追求 MTTR 最优化）；② Spot Instance 成本优化 vs SLA 保证；③ AI 自动化 vs DevOps 文化人本主义——已在 Contradictions 部分详细记录；Entity/Concept 去重：已检查 wiki/entities 和 wiki/concepts，Agentic AI、Self-Healing、RCA、FinOps、Multi-Cloud Strategy 等页面均已存在，仅追加本文档为来源。 + +## [2025-03-02] ingest | The Myths and Misconceptions About Cloud Computing | LinkedIn +- Source file: Cloud & DevOps/The Myths and Misconceptions About Cloud Computing LinkedIn.md +- Status: ✅ 成功摄入 +- Summary: 云计算领域7大常见误解及真相——澄清云安全不如本地、云计算成本高、迁移复杂、性能不可靠等认知误区。核心观点：主流云服务商通过加密、MFA、合规认证（ISO 27001/HIPAA/GDPR）提供比本地更强的安全保障；按需付费模型配合预留实例和自动扩展可显著降低成本；分阶段迁移策略和混合云方案可有效降低迁移风险；SLA 保证可用性通常超过 99.99%。 +- Concepts created: Cloud-Computing（本页面首次创建独立 Concept 页，整合云服务交付12大领域和云成熟度模型相关内容） +- Entities created: 无（ISO-27001、HIPAA、GDPR 已存在于 overview.md，无需新建 Entity 页） +- Source page: wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md +- Notes: index.md Sources 部分已有本条目（line 98），已补全一行摘要；overview.md Cloud Transformation & DevOps 部分新增本 Source 独立 entry，补充7大误解与真相的详细内容，与 [[ctp-topic-53-why-bother-with-cloud]]（云转型商业价值）共同构成云采用决策的知识基础；Entity/Concept 去重：已检查 wiki/entities 和 wiki/concepts 目录，ISO-27001.md、HIPAA.md、GDPR.md 均已存在于 entities 目录，无需新建；Cloud-Computing.md 为本 Source 新建 Concept 页面，整合云服务交付和云成熟度相关内容；冲突检测：与 On-Premises 传统认知在安全性、成本、控制权方面存在观点对立，已在 Source Page Contradictions 部分记录。 + +## [2026-04-27] ingest | Public vs Private vs Hybrid Cloud Differences Explained +- Source file: Cloud & DevOps/Public vs Private vs Hybrid Cloud Differences Explained.md +- Status: ✅ 成功摄入 +- Summary: 公有云、私有云与混合云三种云计算部署模型的系统性对比——从定义、优势、劣势、适用场景四维度展开；强调混合云作为"安全与扩展兼得"的折中方案；提出"共享责任模型"概念，三种云均适用。 +- Concepts created: 无（概念页面 [[CloudComputing]]、[[PublicCloud]]、[[PrivateCloud]]、[[HybridCloud]]、[[SaaS-PaaS-IaaS]]、[[SharedResponsibilityModel]]、[[CloudStrategy]] 已建议在需要时创建） +- Entities created: [[BMC]]（BMC Software — 源文章发布机构） +- Source page: wiki/sources/public-vs-private-vs-hybrid-cloud-differences-explained.md +- Notes: index.md 中该条目已存在（line 207），仅补建了缺失的源页面文件；冲突检测：与 [[cloud-maturity-model]] 存在"云是否减少复杂度"的视角张力，记录于源页面 Contradictions 节。 + +## [2025-12-18] ingest | These 6 Linux Apps Let You Monitor System Resources in Style +- Source file: Cloud & DevOps/These 6 Linux apps let you monitor system resources in style.md +- Status: ✅ 成功摄入 +- Summary: Linux 系统资源监控工具横向评测——6 款工具分 TUI 类（Btop++、Htop、Glances、Bottom）和 GUI 类（Mission Center、Stacer）；作者首推 Btop++（均衡美观与可用性）；TUI 工具适合 SSH 远程场景；GUI 工具提供类 Windows Task Manager 体验；冲突记录：与 Prometheus/Grafana 企业监控方案存在定位差异，两者面向不同场景（单机能见度 vs 多节点集中监控）互补而非互斥 +- Concepts created: 无（TUI 仅在本文档出现 1 次，未达 ≥2 次独立建页阈值；System-Monitoring 已在 overview.md 以 Key Concept 形式引用） +- Entities created: 无（Btop++、Htop、Glances、Bottom、Mission Center、Stacer 仅在本文档出现 1 次，未达 ≥2 次独立建页阈值，保留于 Source Page 内嵌引用；overview.md 已将其列为 Entity 概览） +- Source page: wiki/sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md +- Notes: index.md 该条目已有占位符，更新日期为 [2025-12-16]；overview.md "Linux System Monitoring" 部分（line 417）已包含该 Source 的 Key Concept 引用，[[Btop++]] 等 6 个工具已列为 Entity 概览，无需新建 Entity 页面；冲突检测：与 [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]] 存在定位差异记录于源页面 Contradictions 节。 + +## [2026-04-28] ingest | How to Simplify Multi-Account Deployments Monitoring: Centralized Logs for AWS CloudFormation StackSets +- Source file: Cloud & DevOps/How to Simplify Multi-Account Deployments Monitoring Centralized Logs for AWS CloudFormation StackSets.md +- Status: ✅ 成功摄入 +- Summary: AWS 官方博客（2025-10-24）详解多账户 StackSets 部署的集中日志监控方案——通过 EventBridge Rules 捕获目标账户 CloudFormation 事件，跨账户转发至管理账户 Central Event Bus，写入 CloudWatch Log Group（central-cloudformation-logs），配合 CloudWatch Logs Insights 实现跨账户单一界面监控；log-setup-management.yaml 一次性完成中心基础设施部署、成员账户 EventBridge 规则推送、跨账户 IAM 角色设置三重任务。 +- Concepts created: 无（Centralized Logging/Cross-Account Monitoring/Multi-Account Deployment/StackSets-Deployment-Visibility 各仅在本文档出现 1 次，未达 ≥2 次独立建页阈值，保留于 Source Page 内嵌引用；overview.md 已将其作为 Key Concept 引用） +- Entities created: 无（AWS CloudFormation StackSets/Amazon EventBridge/Amazon CloudWatch Logs/AWS Organizations/AWS KMS 各仅在本文档出现 1 次，未达 ≥2 次独立建页阈值，保留于 Source Page 内嵌引用） +- Source page: wiki/sources/how-to-simplify-multi-account-deployments-monitoring-centralized-logs-for-aws-cloudformation-stacksets.md +- Notes: index.md 该条目已有占位符，更新日期为 [2026-04-26]；overview.md Cloud Transformation & DevOps 部分新增本 Source entry，置于 [[how-can-a-multi-cloud-strategy-transform-your-business-roi]] 之后，与 [[ctp-topic-16-cross-account-terraform-modules]]（跨账号 Terraform 模块）和 [[ctp-topic-67-cloud-native-observability-using-opentelemetry]]（OpenTelemetry 日志链路）建立关联；冲突检测：未发现与其他 Wiki 页面的内容冲突。 diff --git a/wiki/overview.md b/wiki/overview.md index 4caa165f..e7385b92 100644 --- a/wiki/overview.md +++ b/wiki/overview.md @@ -180,6 +180,20 @@ Git 是云转型计划中 DevOps 与 CI/CD 流水线的基础技能。**[[ctp-to **[[ctp-topic-9-ci-cd-with-gruntwork]]**（CTP Topic 9）聚焦 CI/CD 与 Gruntwork 在 AWS Landing Zone 中的实践，基于 Gruntwork 参考架构通过 Terraform/Terragrunt 实现基础设施自动化交付（⚠️ 视频待 Whisper 转录后补充详细内容）。 +**[[devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]]**（DevOps Culture and Transformation）：深入阐述 DevOps 文化转型的完整框架——四大文化支柱（跨职能协作/自动化/持续改进/客户导向）、Agile 与 DevOps 的共生关系（Scrum/Kanban 提供方法论框架，CI/CD 提供工程加速能力）、以及战略转型 playbook（领导层支持 → 团队赋能 → 小步试点 → 克服阻力）。核心洞察：DevOps 本质是文化与思维转变而非工具引入；自动化应覆盖 CI/CD、IaC、可观测性三个层面；无责事后分析（blameless post-mortems）是持续改进的关键机制。未来趋势：AI/ML 赋能智能自动化、GitOps、Serverless DevOps、边缘计算 DevOps、DevSecOps 深化。与 [[ctp-topic-4-using-agile-to-run-the-cloud-transformation-program]]（敏捷落地）和 [[ctp-topic-33-an-introduction-to-gitops]]（GitOps）共同构成完整的 DevOps 知识体系。 + +**[[cloud-devop-maturity-guideline]]**（Cloud DevOp Maturity - Guideline）：企业级 SaaS 公司的云 DevOps 成熟度评估框架与提升路径——基于 DORA 四项核心指标（部署频率、变更前置时间、变更失败率、MTTR）和 CMMI 成熟度模型，从自动化、协作文化、监控可观测性、安全集成（DevSecOps）四大支柱进行系统评估。核心工具链覆盖 CI/CD（持续集成/持续交付流水线）、IaC（Terraform/Ansible 基础设施即代码）、容器化（Kubernetes/Docker）、监控（Prometheus/Grafana）。成熟度提升路线：进行成熟度评估 → 建立 DevOps 卓越中心 → 分阶段实施改进（从 CI/CD 和自动化入手）→ 持续迭代。与 [[devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]]（DevOps 文化转型）共享四大支柱框架但侧重不同——前者聚焦文化转型方法论，后者聚焦量化评估与成熟度路径；与 [[devops-maturity-model-from-traditional-it-to-advanced-devops]] 在 DevOps 成熟度模型层面关联。 + +**[[what-i-know-about-cloud-service-delivery-1]]**（What I Know About Cloud Service Delivery 1）：云服务交付（Cloud Service Delivery）完整生命周期管理框架——核心定义：云服务交付是连接云技术能力（IaaS/PaaS/SaaS）与最终用户实际需求之间的桥梁，由多角色团队（Cloud Infrastructure Engineer / DevOps SRE / Security / FinOps / Support）协作驱动。12 大管理领域：①服务供给与部署（自动化 + 资源配置）；②基础设施管理（监控 + 补丁 + HA/DR）；③平台管理 PaaS（中间件/数据库/开发工具）；④应用运营管理（性能监控 + 持续部署 + 密钥管理）；⑤安全与合规（防火墙/IDS/IPS/IAM + GDPR/HIPAA/PCI）；⑥性能与可用性监控（SLA 99.9% vs 99.99%、SLO、Grafana 告警）；⑦事件与问题管理（Incident/Problem 双层机制）；⑧变更与配置管理（IaC + Planned/Emergency Change 区分）；⑨成本管理与优化（FinOps、Savings Plans、Right-sizing）；⑩客户接入与支持（Onboarding + 服务台）；⑪服务治理与生命周期（Service Catalog + CCOE）；⑫备份恢复与灾难管理（Backup 策略 + DR 演练）。最佳实践工具：AWS CloudWatch + Grafana（监控）、New Relic/APM（应用性能）、WAF + IP Whitelist（安全）、Terraform IaC（配置管理）。属 [[Cloud-DevOps-Maturity-Model]] 在运营管理维度的具体化，与 [[cloud-devop-maturity-guideline]]（成熟度评估）和 [[devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]]（DevOps 文化）共同构成完整的云运营知识体系。 + +**[[cloud-maturity-model-a-detailed-guide-for-cloud-adoption]]**（Cloud Maturity Model - A Detailed Guide For Cloud Adoption）：系统性介绍 **Cloud Maturity Model (CMM)** 云成熟度模型的完整指南——5级成熟度阶段（Level 0 Legacy → Level 5 Optimized）覆盖企业云转型完整路径；关键组成要素覆盖业务维度（财务/战略/组织/文化/治理/合规/采购）和技术维度（架构/应用/DevOps/安全/IaaS/PaaS/SaaS/AI/IoT）；三维评估框架（People/Processes/Technology）；7大收益（战略规划增强、团队协作提升、应用性能提升、安全性增强、上市时间缩短、行业对标、成本节约）；最佳实践（设定云采用目标、识别当前成熟度级别、选择合适的成熟度模型、遵循治理与合规、安全与风险管理）。核心理念：CMM 是云转型的全面导航仪，帮助企业找到适合自身需求的平衡点，Level 5 是目标但往往更具理想性，建议选择性采纳带来明确业务价值的要素。与 [[cloud-devop-maturity-guideline]] 在成熟度模型层面互补——前者聚焦 DevOps 交付能力成熟度，本 Source 聚焦云采用全维度成熟度；与 [[devops-maturity-model-from-traditional-it-to-advanced-devops]] 共同构成完整成熟度知识体系。 + +**[[the-myths-and-misconceptions-about-cloud-computing-linkedin]]**（The Myths and Misconceptions About Cloud Computing | LinkedIn）：云计算领域7大常见误解及真相——澄清云安全不如本地、云计算成本高、迁移复杂、性能不可靠等认知误区。核心观点：主流云服务商通过加密、MFA、合规认证（ISO 27001/HIPAA/GDPR）提供比本地更强的安全保障；按需付费模型配合预留实例和自动扩展可显著降低成本；分阶段迁移策略和混合云方案可有效降低迁移风险；SLA 保证可用性通常超过 99.99%。属 [[Cloud-Computing]] 认知纠正的基础入门，与 [[ctp-topic-53-why-bother-with-cloud]]（云转型商业价值）共同构成云采用决策的知识基础。 + +**[[how-can-a-multi-cloud-strategy-transform-your-business-roi]]**（How Can a Multi Cloud Strategy Transform Your Business ROI?）：多云策略（Multi-Cloud Strategy）的商业价值与实施框架——核心数据：78% 企业使用 3+ 公有云、86% 企业计划 2024 年底采用多云、优化后实现 30% 运营成本降低（Forrester）。8 大商业价值：①避免供应商锁定（保留谈判筹码）、②增强弹性与可用性（跨云冗余 99.99%）、③提升安全态势（各云最佳安全功能）、④无限弹性扩展（应对流量高峰）、⑤成本优化（跨提供商比价）、⑥加速创新（访问最新云服务）、⑦满足合规（数据主权控制）、⑧性能优化（选择最近/最快的云区域）。行业案例：电商高峰期跨云扩展、医疗机构 HIPAA 合规、金融机构多云安全。实施路径：评估需求→选择提供商（对齐服务与需求）→集成管理（Kubernetes/Terraform）→监控优化（CloudHealth/Datadog）。属 [[Multi-Cloud-Strategy]] 概念的核心来源，与 [[cloud-operating-model-key-strategies-and-best-practices]] 中的"统一治理"形成互补——多云是选择层，Cloud Operating Model 是治理层；与 [[Vendor-Lock-In]] 共同构成云供应商风险管理知识体系。 + +**[[how-to-simplify-multi-account-deployments-monitoring-centralized-logs-for-aws-cloudformation-stacksets]]**（How to Simplify Multi-Account Deployments Monitoring: Centralized Logs for AWS CloudFormation StackSets）：AWS 官方博客（2025-10-24）详解多账户 StackSets 部署的集中日志监控方案——解决当跨 50 个账户部署关键安全基线突然失败时，团队需逐个登录账户查看日志的运营痛点。核心架构：①管理账户部署（log-setup-management.yaml）创建 Central Event Bridge Bus + CloudWatch Log Group（central-cloudformation-logs）+ KMS 加密；②通过同一 StackSet 自动向所有成员账户推送 EventBridge Rules；③StackSet 部署模板（common-resources-stackset.yaml）在目标账户创建 S3 等通用资源并触发 CloudFormation 事件。事件流：目标账户 CloudFormation 事件 → EventBridge Rules（按模式捕获）→ 跨账户 Event Bus → CloudWatch Log Group → CloudWatch Logs Insights 自定义查询。单一部署三重价值：创建中心日志基础设施 + 自动向所有成员账户推送 EventBridge 规则 + 设置跨账户 IAM 角色。成本组件：EventBridge 跨账户事件费 + CloudWatch Logs 存储与查询费 + KMS 密钥费。与 [[ctp-topic-16-cross-account-terraform-modules]]（跨账号 Terraform 模块）共享跨账户 IAM Assume Role 机制但聚焦维度不同——前者解决部署工具的跨账户访问，后者解决 StackSets 部署本身的可见性问题；与 [[what-i-know-about-cloud-service-delivery-1]] 中"性能与可用性监控"和[[ctp-topic-67-cloud-native-observability-using-opentelemetry]]（OpenTelemetry 日志链路）共同构成企业级可观测性知识体系。 + Cloud Transformation Programme (CTP) materials cover AWS landing zones, EKS, Terraform, GitOps, FinOps, observability, security, and enterprise architecture. Key themes: 3 Lines of Defence framework, ITSM, container hardening, backup & DR strategies. DevOps culture focuses on four pillars: Collaboration, Automation (CI/CD, IaC), Continuous Improvement (Kaizen), and Customer-Centricity. Agile practices (Scrum, Kanban) are symbiotic with DevOps. Emerging trends: DevSecOps, GitOps, Serverless DevOps, AI/ML-driven automation, and Edge Computing DevOps. **[[ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments]]**（CTP Topic 32）：Atlantis 替代 Jenkins 用于 Terraform IaC 部署——针对当前 Jenkins 流水线初始化慢（多次代码克隆/顺序测试/ECS 预配置）和架构复杂（持续叠加功能导致脆弱）的双重痛点，Atlantis 提供 PR 评论式协作模型，开发者直接在 GitHub PR 上评论 `atlantis plan`/`apply` 即可触发变更，无需独立账号；每个 Landing Zone 共享账户部署单台 EC2 实例，通过 GitHub Enterprise Webhook 接收通知，服务账号负责评论/合并/关闭 PR；跨账户访问通过在各账户部署的 IAM 角色实现；并行构建支持多模块并发 plan/apply；锁定机制防止多 PR 同时操作同一模块产生冲突。Atlantis 在 merge 前即应用变更，确保代码与基础设施始终同步。属 [[GitOps]] 工具实践层，与 [[ctp-topic-33-an-introduction-to-gitops]]（GitOps 概念）和 [[ctp-topic-9-ci-cd-with-gruntwork]]（Gruntwork CI/CD）共同构成完整链路。注意：[[ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone]] 提到 Atlantis 当前不支持 EKS 部署，两者存在实践约束差异。 @@ -350,6 +364,8 @@ Key concepts: [[Process]], [[Value]], [[Value-Stream]], [[Value-Adding]], [[Wast **[[ctp-topic-72-enterprise-dr-strategy-aws-backup]]**（CTP Topic 72）：AWS 解决方案架构师 Sabith 深入讲解企业级灾难恢复策略与 AWS Backup 架构设计——核心内容：HA（高可用）关注系统运行时间和 MTBF，DR（灾难恢复）专注于防止数据丢失和系统恢复，两者互补；RPO（恢复点目标）定义可接受的最大数据丢失量，RTO（恢复时间目标）定义可接受的最大停机时间；AWS Backup 完全托管、基于策略，通过 Backup Plans 定义何时备份什么，Backup Vaults 存储恢复点，支持跨账户跨区域复制；四级 DR 架构模式（Backup and Restore → Pilot Light → Warm Standby → Active-Active）提供从低成本到高弹性的递进选择；增量备份仅捕获变更，节省成本；Vault Lock 合规模式防止任何人（包括根用户）提前删除恢复点，有效防勒索软件；建议使用独立的 Vault/Bunker Account 存储备份副本，取证账户（Forensic Account）定期测试恢复点并扫描恶意软件。属 [[AWS-Landing-Zone]] DR 与数据保护层的理论基础补充，与 [[ctp-topic-44-aws-backup-in-micro-focus]]（聚焦 Micro Focus 内部评估）和 [[ctp-topic-73-aws-backup-implementation]]（聚焦 CTP 迁移实施）构成完整的 AWS Backup 知识体系。 +**[[rto-vs-rpo-key-differences-for-modern-disaster-recovery]]**（RTO vs RPO: Key Differences for Modern Disaster Recovery）：RTO（Recovery Time Objective）和 RPO（Recovery Point Objective）在现代灾难恢复与持续交付中的关键区别与实践应用——核心区分：RTO 衡量系统停机时长容忍度（从故障时刻开始计时），RPO 衡量数据丢失容忍度（从上一备份时刻向前测量）；现代部署环境下软件故障（Bug/错误迁移/AI 模型异常）比硬件灾难更频繁，每日常规发布即潜在 RTO/RPO 场景。Feature Flag 驱动的新范式：通过部署与发布解耦（Deploy whenever you want, release when you're ready）、渐进式灰度发布（1%→5%→25%→100%）和 Kill Switch（即时禁用故障功能），将 RTO 从"小时级紧急回滚部署"缩短至"秒级配置开关切换"，RPO 通过 Feature Flag 保护数据完整性避免回滚时数据损坏。应用分层恢复策略：Tier 1 Critical（支付/认证，RTO<5min/RPO<1min）→ Tier 2 Important（管理后台/报表，RTO<1h/RPO<15min）→ Tier 3 Nice-to-have（内部工具，RTO<4h/RPO<1h）。成本效益原则：若停机1小时损失 $10K，不要每年花 $100K 基础设施预防——Feature Flag 方案比传统热备基础设施成本更低、效果更好（HP/Christian Dior 案例）。属 [[ctp-topic-72-enterprise-dr-strategy-aws-backup]]（AWS 基础设施层 DR）在软件交付层的互补——前者聚焦备份基础设施，后者聚焦代码层快速恢复，共同构成完整 DR 知识体系；与 [[what-i-know-about-cloud-service-delivery-1]]（"备份恢复与灾难管理"第12领域）形成引用关系；与 [[cloud-devop-maturity-guideline]] 的 DORA MTTR 指标关联（MTTR 直接量化 RTO）。 + **[[Install WSL]]**（[[install-wsl]]）：微软官方 WSL 完整安装指南——`wsl --install` 一键安装（Windows 10/11 Build 19041+），支持 Ubuntu/Debian/SUSE/Kali 等多发行版并行安装，`wsl.exe --set-default-version` 切换 WSL1/WSL2；离线场景通过 MSI + DISM 命令手动启用 Virtual Machine Platform；运行入口推荐 Windows Terminal（含多标签、自定义快捷键）。[[Install WSL]] 与 [[WSL2 启动与网络配置指南]] 互补——前者解决安装问题，后者解决网络配置问题。 **[[WSL2]]** 是 Windows 内置的 Linux 运行环境，WSL2 默认使用 NAT 网络模式导致 Windows 代理无法被 WSL2 内部访问。通过 `.wslconfig` 启用 `networkingMode=mirrored` + `dnsTunneling=true` 可实现 WSL2 与 Windows 共享网络堆栈；国内环境下可使用 `ghproxy.com` 反向代理加速 GitHub 下载。[[WSL2]] 与 [[Ubuntu Server]] 同属 Linux 环境，[[WSL2]] 侧重 Windows 桌面开发场景，[[Ubuntu Server]] 侧重无头服务器场景。 diff --git a/wiki/sources/cloud-devop-maturity-guideline.md b/wiki/sources/cloud-devop-maturity-guideline.md index 4f525c87..527f92a3 100644 --- a/wiki/sources/cloud-devop-maturity-guideline.md +++ b/wiki/sources/cloud-devop-maturity-guideline.md @@ -1,73 +1,49 @@ -# Cloud DevOp Maturity - Guideline - -## Source File -- [[raw/Cloud & DevOps/Cloud DevOp Maturity - Guideline.md]] - -## Metadata -- **title**: Cloud DevOp Maturity - Guideline -- **author**: shenwei -- **published**: -- **created**: -- **tags**: [] - -## Summary - -A comprehensive guideline for evaluating cloud DevOps maturity in enterprise-level SaaS organizations. The document outlines 8 key areas: definition of maturity, maturity models (CMMI, DORA), foundational pillars (Automation, Collaboration, Monitoring, Security), tooling choices, measurement metrics, challenges, case studies, and a roadmap for achieving higher maturity levels. - -## Key Topics Covered - -### 1. Definition of Cloud DevOps Maturity -- DevOps maturity encompasses automation, collaboration between development and operations, speed of delivery, and reliability -- Business case: reducing time-to-market, improving operational efficiency, enhancing product reliability - -### 2. Key Maturity Models -- **CMMI** (Capability Maturity Model Integration) -- **DORA** (DevOps Research & Assessment) metrics: - - Deployment frequency - - Lead time for changes - - Change failure rate - - Mean Time to Recovery (MTTR) - -### 3. Foundational Pillars -- **Automation**: CI/CD pipelines, IaC, test automation -- **Collaboration and Culture**: Cross-team collaboration, breaking down silos -- **Monitoring and Observability**: Continuous monitoring, logging, swift issue resolution -- **Security Integration (DevSecOps)**: Security automated into DevOps lifecycle - -### 4. Tooling and Technology -- DevOps Toolchain: CI/CD, IaC (Terraform, Ansible), Containerization (Kubernetes, Docker) -- Monitoring: Prometheus, Grafana -- Cloud-native practices: microservices, serverless - -### 5. Metrics for Measuring Maturity -- **KPIs**: Deployment frequency, lead times, system uptime, incident resolution times -- **Qualitative measures**: Employee collaboration, goal alignment, feedback loops - -### 6. Challenges -- Resistance to change -- Scaling DevOps globally -- Regulatory and compliance constraints - -### 7. Roadmap -- Conduct DevOps maturity assessment -- Build a DevOps Center of Excellence -- Implement phased improvements (starting with CI/CD and automation) -- Ongoing iteration and continuous improvement - -## Related Sources -- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] — Traditional IT to Advanced DevOps maturity model -- [[sources/cloud-operating-model-key-strategies-and-best-practices.md]] — Cloud operating model strategies -- [[sources/what-is-devsecops-best-practices-benefits-and-tools.md]] — DevSecOps practices and tools -- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]] — Cloud maturity model guide -- [[sources/how-agentic-ai-can-help-for-cloud-devops.md]] — AI for Cloud DevOps - -## Concepts Extracted -- [[concepts/DevOps-Maturity]] -- [[concepts/DORA-Metrics]] -- [[concepts/DevSecOps]] -- [[concepts/CI-CD-Pipeline]] -- [[concepts/Infrastructure-as-Code]] -- [[concepts/Cloud-Native]] - -## Ingested -- Date: 2026-04-21 +--- +title: "Cloud DevOp Maturity - Guideline" +type: source +tags: [cloud, devops, maturity, enterprise, saas] +date: 2026-04-26 +--- + +## Source File +- [[Cloud & DevOps/Cloud DevOp Maturity - Guideline.md]] + +## Summary（用中文描述） +- 核心主题：企业级 SaaS 公司的云 DevOps 成熟度评估框架与提升路径 +- 问题域：如何定义、衡量和提升云端 DevOps 实践的成熟度 +- 方法/机制：基于 DORA 四大指标（部署频率、变更前置时间、变更失败率、平均恢复时间）和 CMMI 成熟度模型，从自动化、协作文化、监控可观测性、安全集成四大支柱进行评估 +- 结论/价值：DevOps 成熟度提升是持续迭代过程，需分阶段实施，从 CI/CD 和自动化入手，逐步建立 DevOps 卓越中心 + +## Key Claims（用中文描述） +- 企业通过评估 DevOps 成熟度，可缩短上市时间、提升运营效率并增强产品可靠性 +- DORA 四项核心指标（部署频率、变更前置时间、变更失败率、MTTR）是衡量 DevOps 绩效的行业标准 +- 成熟的 DevOps 组织需在自动化（CI/CD、IaC、测试自动化）、跨团队协作与文化、监控可观测性、安全集成（DevSecOps）四大支柱上均衡发展 +- 云原生架构（微服务、容器化、无服务器技术）可加速 DevOps 成熟度提升 +- DevOps 成熟度提升路径包括：进行成熟度评估 → 建立 DevOps 卓越中心 → 分阶段实施改进（从 CI/CD 和自动化开始）→ 持续迭代 + +## Key Quotes +> "Focus on CI/CD pipelines, infrastructure as code (IaC), and test automation. Emphasize the importance of repeatable and reliable deployments." — 自动化是成熟 DevOps 的基石 +> "DevOps is a continuous improvement process, and even mature companies need to adapt to evolving technologies and practices." — DevOps 成熟度提升是持续迭代过程 + +## Key Concepts +- [[DevOpsMaturityModel]]：CMMI 和 DORA 模型定义的组织 DevOps 能力成熟度等级体系 +- [[DORAMetrics]]：DevOps Research & Assessment 的四大核心指标——部署频率、变更前置时间、变更失败率、平均恢复时间（MTTR） +- [[CI/CDPipeline]]：持续集成/持续交付流水线，DevOps 自动化的核心机制 +- [[InfrastructureAsCode]]：通过代码管理基础设施，实现环境一致性和可重复部署 +- [[DevSecOps]]：将安全集成到 DevOps 全生命周期，实现持续安全合规 +- [[MicroservicesArchitecture]]：云原生微服务架构，支持独立部署和快速迭代 +- [[Observability]]：可观测性，通过持续监控、日志和追踪快速发现和解决生产问题 + +## Key Entities +- [[CMMI]]：Capability Maturity Model Integration，能力成熟度模型集成，用于定义组织过程改进的成熟度等级 +- [[DORA]]：DevOps Research & Assessment，DevOps 研究与评估组织，提供行业标准的 DevOps 绩效指标 + +## Connections +- [[DevOpsMaturityModel]] ← based_on ← [[DORAMetrics]] +- [[CI/CDPipeline]] ← core_enabler ← [[DevOpsMaturityModel]] +- [[InfrastructureAsCode]] ← supports ← [[CI/CDPipeline]] +- [[DevSecOps]] ← extends ← [[DevOpsMaturityModel]] +- [[MicroservicesArchitecture]] ← architectural_pattern ← [[CloudNativePractices]] + +## Contradictions +- 暂无已知的 Wiki 内冲突内容 diff --git a/wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md b/wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md index 651eaeb9..9890d57f 100644 --- a/wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md +++ b/wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md @@ -1,63 +1,84 @@ ---- -title: Cloud Maturity Model - A Detailed Guide For Cloud Adoption -source: https://www.bacancytechnology.com/blog/cloud-maturity-model -author: shenwei -published: 2024-07-08 -created: 2025-02-28 -description: Explore the Cloud Maturity Model (CMM) with key components, benefits, and stages, and optimize processes with best practices for successful cloud adoption. -tags: [Cloud, Cloud Adoption, Maturity Model, CMM, CMM 4.8, Cloud Native, CSMM, SAMM, AWS CAF, Azure CAF, GCP CAF] -link: ---- - -## Source File -- [[raw/Cloud & DevOps/Cloud Maturity Model A Detailed Guide For Cloud Adoption.md]] - -## Summary - -本文档系统性介绍了 **Cloud Maturity Model (CMM)** 云成熟度模型，包含以下核心内容： - -- **5个成熟度阶段**：从 Level 0（无云就绪）到 Level 5（优化级），覆盖企业云转型的完整路径 -- **关键组成要素**：从业务（财务、战略、组织、文化、治理、合规、采购等）和技术（架构、应用、DevOps、安全、IaaS/PaaS/SaaS、AI/IoT等）两个维度评估 -- **三大评估维度**：People（人员）、Processes（流程）、Technology（技术） -- **7大收益**：战略规划增强、团队协作提升、应用性能提升、安全性增强、上市时间缩短、行业对标、成本节约 -- **最佳实践**：设定云采用目标、识别当前成熟度级别、选择合适的成熟度模型、遵循治理与合规、安全与风险管理 -- **主流云成熟度模型对比**：CMM 4.8、Cloud Native Maturity Model、CSMM、SAMM、AWS CAF、Azure CAF、Google Cloud CAF - -## Key Takeaways - -- Forrester 预测全球云成熟度模型行业到 2025 年将达 15 亿美元 -- Gartner 指出超过 60% 的组织正在积极实施云成熟度模型 -- 成熟度模型不是追求完全上云，而是找到适合组织需求的平衡点 -- Level 5 是目标但往往更具理想性，建议选择性采纳带来明确业务价值的要素 -- 跨越低级别（如管理和流程定义）可能导致后续挑战和不必要的成本 - -## Key Entities - -- [[Cloud Maturity Model]] — 主体框架 -- [[Cloud Native Maturity Model]] — 云原生成熟度模型 -- [[Cloud Security Maturity Model]] — 云安全成熟度模型 -- [[Software Assurance Maturity Model]] — 软件保障成熟度模型（SAMM） -- [[AWS Cloud Adoption Framework]] — AWS 云采用框架 -- [[Azure Cloud Adoption Framework]] — Azure 云采用框架 -- [[Google Cloud Adoption Framework]] — Google Cloud 云采用框架 -- [[Open Alliance for Cloud Adoption]] — OACA 云采用联盟 -- [[Cloud Maturity Levels]] — 成熟度5级模型 -- [[Cloud Adoption Strategy]] — 云采用策略 - -## Concepts - -- [[Cloud Adoption]] — 云采用 -- [[Cloud Migration]] — 云迁移 -- [[Cloud Governance]] — 云治理 -- [[Cloud Security]] — 云安全 -- [[FinOps]] — 云财务管理 -- [[Cloud-Native]] — 云原生 -- [[Cloud Cost Optimization]] — 云成本优化 -- [[Multi-Cloud Strategy]] — 多云策略 -- [[Hybrid Cloud]] — 混合云 -- [[People-Process-Technology]] — 人-流程-技术三维评估 -- [[Cloud Center of Excellence]] — 云卓越中心（CCoE） -- [[GAP Analysis]] — 差距分析 -- [[Cloud Compliance]] — 云合规 -- [[CAPEX vs OPEX]] — 资本支出vs运营支出 -- [[TCO (Total Cost of Ownership)]] — 总拥有成本 +--- +title: "Cloud Maturity Model - A Detailed Guide For Cloud Adoption" +type: source +tags: [Cloud, Cloud Adoption, Maturity Model, CMM, Cloud Native, CSMM, SAMM, AWS CAF, Azure CAF, GCP CAF] +date: 2024-07-08 +--- + +## Source File +- [[raw/Cloud & DevOps/Cloud Maturity Model A Detailed Guide For Cloud Adoption.md]] + +## Summary（用中文描述） + +- **核心主题**：Cloud Maturity Model（CMM）云成熟度模型——系统性评估企业云采用成熟度并指导其向更高阶段演进的结构化框架 +- **问题域**：企业云转型过程中，如何评估当前状态、识别差距、制定演进路线 +- **方法/机制**：5级成熟度模型（Level 0–5）从业务维度（财务/战略/组织/文化/治理/合规/采购）和技术维度（架构/应用/DevOps/安全/IaaS/PaaS/SaaS/AI/IoT）进行三维评估（People/Processes/Technology）；7大收益；最佳实践；7种主流成熟度模型对比 +- **结论/价值**：CMM 是云转型成功的导航仪，帮助企业找到适合自身需求的平衡点，避免盲目追高或止步不前 + +## Key Claims（用中文描述） + +- Forrester 预测全球云成熟度模型行业到 2025 年将达 15 亿美元，反映企业云成熟度管理的巨大市场需求 +- Gartner 指出超过 60% 的组织正在积极实施云成熟度模型，说明其已成为云转型主流实践 +- Open Alliance for Cloud Adoption（OACA）定义的 CMM 帮助组织识别云采用痛点、评估当前状态、设定未来目标并执行 GAP 分析 +- 云成熟度模型不是追求完全上云，而是找到适合组织需求的平衡点 +- Level 5 是目标但往往更具理想性，建议选择性采纳带来明确业务价值的要素，避免跨越低级别导致后续挑战 +- 跨越低级别（如管理和流程定义）可能导致后续成熟度旅程中的挑战和不必要的成本 + +## Key Quotes + +> "CMMs are crucial because they offer a structured approach to assessing your current cloud adoption strategy. They help you avoid common pitfalls and identify areas of improvement." — CMM 的核心价值定位 + +> "It is common for organizations only partially to reach level 4. Some parts of their cloud capabilities may still be at levels 2 or 3." — Level 4 部分成熟现象 + +> "Achieving this fifth level is often more aspirational than real for many." — Level 5 的理想与现实差距 + +## Key Concepts + +- [[Cloud Adoption]]：云采用——组织将工作负载和服务迁移至云平台并持续优化的过程 +- [[Cloud Migration]]：云迁移——将应用/数据/工作负载从本地迁移至云端的具体行动 +- [[Cloud Governance]]：云治理——建立云环境中的策略、角色、风险管理框架 +- [[Cloud Security]]：云安全——云环境中的数据保护、访问控制、合规遵循 +- [[FinOps]]：云财务管理——云资源使用的成本优化与财务可见性管理 +- [[Cloud-Native]]：云原生——充分利用云平台弹性、可扩展、自动化特性的架构方法 +- [[Cloud Cost Optimization]]：云成本优化——通过右置资源、自动化、监控实现云支出效率最大化 +- [[Multi-Cloud Strategy]]：多云策略——同时使用多个云服务商以避免供应商锁定 +- [[Hybrid Cloud]]：混合云——结合公有云弹性与私有云合规/安全的混合部署模式 +- [[People-Process-Technology]]：人-流程-技术三维评估框架——评估组织云成熟度的三个核心维度 +- [[Cloud Center of Excellence]]（CCoE）：云卓越中心——推动组织云能力的跨职能专家团队 +- [[GAP Analysis]]：差距分析——评估当前状态与目标状态之间差距的系统性方法 +- [[Cloud Compliance]]：云合规——确保云操作符合 HIPAA/PCI-DSS 等行业法规 +- [[CAPEX vs OPEX]]：资本支出 vs 运营支出——云迁移带来的财务模式转变 +- [[TCO (Total Cost of Ownership)]]：总拥有成本——包含直接成本、间接成本、隐性成本的全成本视角 + +## Key Entities + +- [[Cloud Maturity Model]]：主体框架——5级成熟度评估模型 +- [[Cloud Native Maturity Model]]：CNCF 云原生成熟度模型——指导云原生技术采用的专项模型 +- [[Cloud Security Maturity Model]]（CSMM）：云安全成熟度模型——IANS/Securosis 的云安全评估框架 +- [[Software Assurance Maturity Model]]（SAMM）：软件保障成熟度模型——覆盖完整软件生命周期的技术/流程中立框架 +- [[AWS Cloud Adoption Framework]]（AWS CAF）：AWS 云采用框架——AWS 提供的云转型指导 +- [[Azure Cloud Adoption Framework]]（Azure CAF）：Azure 云采用框架——Microsoft Azure 提供的云转型最佳实践 +- [[Google Cloud Adoption Framework]]（GCP CAF）：Google Cloud 云采用框架——Google Cloud 的云转型路线 +- [[Open Alliance for Cloud Adoption]]（OACA）：云采用联盟——定义 CMM 的行业组织 +- [[Cloud Maturity Levels]]：成熟度5级——Level 0（Legacy）→ Level 5（Optimized） + +## Connections + +- [[Cloud Maturity Model]] ← evaluates ← [[Cloud Adoption Strategy]] +- [[Cloud Maturity Model]] ← defined_by ← [[Open Alliance for Cloud Adoption]] +- [[Cloud Maturity Levels]] ← part_of ← [[Cloud Maturity Model]] +- [[Cloud Native Maturity Model]] ← extends ← [[Cloud Maturity Model]]（专项领域扩展） +- [[Cloud Security Maturity Model]] ← extends ← [[Cloud Maturity Model]]（安全专项） +- [[AWS Cloud Adoption Framework]] ← competes_with ← [[Azure Cloud Adoption Framework]] +- [[AWS Cloud Adoption Framework]] ← competes_with ← [[Google Cloud Adoption Framework]] +- [[Cloud Cost Optimization]] ← enables ← [[FinOps]] +- [[Cloud Governance]] ← depends_on ← [[Cloud Compliance]] +- [[DevOps Maturity Model]] ← related_to ← [[Cloud Maturity Model]]（两者均评估组织技术能力成熟度） + +## Contradictions + +- 与 [[DevOps Maturity Model]] 在"成熟度框架"上的视角差异： + - 冲突点：DevOps 成熟度聚焦研发交付能力，CMM 聚焦云采用整体成熟度 + - 当前观点（本文）：CMM 是云转型的全面导航，覆盖人员/流程/技术全维度 + - 对方观点（DevOps）：DevOps 成熟度更聚焦软件交付速度和稳定性 + - 说明：两者为互补关系而非互斥，组织可同时评估和提升两个维度的成熟度 diff --git a/wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md b/wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md index 754962c4..7ca85110 100644 --- a/wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md +++ b/wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md @@ -1,63 +1,51 @@ ---- -title: "DevOps Culture and Transformation: Fostering Collaboration, Agile Practices, and Innovation" -type: source -tags: [devops, agile, cloud, transformation] -date: 2026-04-17 -source_file: raw/Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md ---- - -## Source File -- [[raw/Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md]] - -## Summary -This LinkedIn article by Hemant Sawant provides a comprehensive guide to DevOps culture and organizational transformation. It covers the four foundational pillars of DevOps (collaboration, automation, continuous improvement, and customer-centricity), how to integrate Agile practices, and a strategic playbook for driving DevOps transformation at scale. The article also outlines future trends including AI/ML in DevOps, GitOps, Serverless DevOps, and Edge Computing DevOps. - -## Key Claims - -### DevOps Pillars -- DevOps dismantles silos between Development and Operations through cross-functional teams that share ownership of the entire software lifecycle -- Automation eliminates manual toil, reduces errors, and accelerates feedback loops — covering CI/CD, IaC, and monitoring/observability -- Continuous Improvement (Kaizen) requires blameless post-mortems, metrics-driven bottleneck identification, and chaos engineering -- Customer-Centricity means embedding feedback loops via feature flagging and A/B testing - -### Agile + DevOps Integration -- Agile and DevOps are symbiotic — Agile provides iterative development, DevOps extends agility to operations -- Shift-Left practices bring operations concerns (security, performance) into the development phase -- Value Stream Mapping visualizes workflows to eliminate waste and streamline handoffs - -### Transformation Strategy -- Leadership buy-in is essential — executives must champion collaboration and allocate resources -- Upskilling through certifications (AWS DevOps, Kubernetes) and internal communities of practice (Guilds/CoEs) is critical -- Pilot projects should demonstrate quick wins before enterprise-wide rollout -- Resistance must be addressed by emphasizing that automation frees teams for higher-value work - -### Future Trends -- AI and ML for intelligent automation in code reviews, anomaly detection, and self-healing infrastructure -- GitOps as the standard for managing infrastructure via Git as the single source of truth -- Serverless DevOps reducing operational overhead via FaaS (e.g., AWS Lambda) -- Edge Computing and IoT DevOps enabling real-time performance optimization closer to end-users -- DevSecOps embedding security more deeply into CI/CD workflows - -## Key Quotes - -> "DevOps isn't just about tools or automation; it's a mindset shift that prioritizes collaboration, continuous learning, and customer-centricity." - -> "DevOps isn't a checkbox—it's a continuous evolution." - -## Connections - -### Related Entities -- [[Hemant Sawant]] — Author of this LinkedIn article - -### Related Concepts -- [[DevOps Culture]] — Core cultural principles covered in this article -- [[CI/CD Pipeline]] — Key automation enabler discussed -- [[Infrastructure as Code (IaC)]] — Automation pillar of DevOps -- [[DevSecOps]] — Shift-Left security integration -- [[GitOps]] — Future trend for infrastructure management -- [[Agile Practices]] — Complementary methodology integrated with DevOps -- [[Continuous Improvement (Kaizen)]] — Japanese philosophy applied to DevOps -- [[Value Stream Mapping]] — Lean technique for DevOps workflow optimization -- [[Feature Flagging]] — Customer feedback mechanism in DevOps -- [[Chaos Engineering]] — Proactive resilience testing -- [[Shift-Left Testing]] — Moving testing earlier in the development lifecycle +--- +title: "DevOps Culture and Transformation: Fostering Collaboration, Agile Practices, and Innovation" +type: source +tags: [] +date: 2025-03-02 +--- + +## Source File +- [[Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn]] + +## Summary（用中文描述） +- 核心主题：DevOps 文化转型 —— 如何通过打破开发与运维之间的壁垒，推动组织实现更快、更可靠的软件交付与持续创新。 +- 问题域：传统 IT 组织中开发团队与运维团队的目标冲突（开发追求快速交付，运维追求稳定），以及组织文化变革的挑战。 +- 方法/机制：四大 DevOps 文化支柱（协作、自动化、持续改进、客户导向）；Agile 与 DevOps 的融合实践；战略转型 playbook（领导层支持、团队赋能、小步试点、克服阻力）。 +- 结论/价值：DevOps 不仅是工具和自动化，而是一场文化变革；拥抱 DevOps 文化 tenets、赋能团队、整合 Agile 实践的组织将在数字时代获得竞争优势。 + +## Key Claims（用中文描述） +- DevOps 通过建立跨职能团队，使开发和运维共同承担整个软件生命周期的责任，从而打破传统 IT 组织中的孤岛现象。 +- 自动化（CI/CD 流水线、基础设施即代码、可观测性工具）是 DevOps 的核心驱动力，能消除人工重复劳动、减少错误、加速反馈循环。 +- DevOps 强调持续改进（Kaizen），通过无责事后分析（blameless post-mortems）、数据指标和混沌工程驱动团队迭代学习。 +- Agile 与 DevOps 具有共生关系 —— Agile 关注迭代开发，DevOps 将敏捷延伸到运维，两者共同实现端到端的速度与质量。 +- DevOps 转型需要领导层支持、小步试点快速验证、用成功案例建立势能，而非一次性大爆炸式推行。 +- DevOps 的未来趋势包括：AI/ML 赋能智能自动化、GitOps、Serverless DevOps、边缘计算与 IoT DevOps、以及 DevSecOps 的深化。 + +## Key Quotes +> "DevOps isn't just about tools or automation; it's a mindset shift that prioritizes collaboration, continuous learning, and customer-centricity." — 核心论点：DevOps 本质是文化与思维转变 +> "Blameless post-mortems to dissect failures without finger-pointing." — DevOps 文化的关键实践：无惧失败、聚焦改进 + +## Key Concepts +- [[DevOps Culture]]：一种打破开发与运维壁垒、以协作、自动化、持续学习和客户导向为核心的文化与运营模式 +- [[CI/CD Pipeline]]：自动化测试、集成和部署流水线，是 DevOps 自动化能力的关键实现 +- [[Infrastructure as Code (IaC)]]：通过代码管理基础设施，实现一致性和版本控制的实践 +- [[Kaizen (Continuous Improvement)]]：持续改进理念，通过无责复盘、数据驱动决策和混沌工程推动迭代优化 +- [[Shift-Left]]：将安全、性能等运维关注点前移至开发阶段，DevSecOps 是其典型实践 +- [[Value Stream Mapping]]：价值流图析，通过可视化工作流识别等待、审批和测试环节的延迟，消除浪费 +- [[GitOps]]：使用 Git 作为唯一真实来源来管理基础设施和部署的运维模式，是 DevOps 的进化方向之一 +- [[Serverless DevOps]]：利用函数即服务（FaaS）等无服务器技术减少运维负担的 DevOps 实践 +- [[Agile-DevOps Integration]]：Agile 与 DevOps 的协同机制，Scrum/Kanban 提供方法论框架，CI/CD 提供工程加速能力 + +## Key Entities +- [[Hemant Sawant]]：LinkedIn 文章原作者，DevOps 文化与转型领域的分享者 +- [[Shenwei]]：本文档的保存整理者 + +## Connections +- [[DevOps Maturity Model]] ← extends ← [[DevOps Culture]]：本文聚焦 DevOps 文化转型，与成熟度模型互为补充（文化层 vs 能力层级） +- [[DevSecOps Best Practices]] ← depends_on ← [[DevOps Culture]]：DevSecOps 是 DevOps 文化中"安全性嵌入"支柱的具体实现 +- [[Agile-DevOps Integration]] ← extends ← [[DevOps Culture]]：Agile 与 DevOps 的融合是本文第二大主题 +- [[How Agentic AI Can Help Cloud DevOps]] ← relates_to ← [[DevOps Culture]]：AI/ML 赋能 DevOps 是本文未来趋势之一 + +## Contradictions +- （本文档为新摄入来源，暂无已知冲突点） diff --git a/wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md b/wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md index 2dbd839d..e5502ab0 100644 --- a/wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md +++ b/wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md @@ -1,184 +1,68 @@ -# DevOps Maturity Model From Traditional IT to Advanced DevOps - -## Source File -- [[raw/Cloud & DevOps/DevOps Maturity Model From Traditional IT to Advanced DevOps.md]] - -## Metadata -- **Source**: https://www.bacancytechnology.com/blog/devops-maturity-model -- **Author**: shenwei -- **Published**: 2024-08-14 -- **Created**: 2025-03-01 -- **Description**: Explore the DevOps Maturity Model: its five stages, benefits, progress metrics, security considerations & how to avoid challenges for effective implementation. - -## Quick Summary - -The blog covers the DevOps Maturity Model, exploring its key components and the five distinct stages of maturity. We'll uncover how adopting this model revolutionizes your organization, enhances security practices, and tackles common challenges you might face. By offering actionable insights, we aim to guide you through measuring and optimizing your DevOps journey, ensuring continuous improvement and long-term success. - -## What is the DevOps Maturity Model? - -The DevOps maturity model is a structured framework that guides organizations through adopting and implementing DevOps principles. This model helps assess an organization's current DevOps practices, identify improvement areas, and outline steps to advance to higher maturity levels. It also evaluates your DevOps practices, covering aspects such as collaboration, release speed, and quality, adherence to principles, use of automation, and tool sets. This DevOps Maturity Model assessment allows organizations to: - -- Analyze and measure their current DevOps capabilities and methodologies. -- Establish benchmarks for their existing DevOps practices. -- Define their target maturity level. -- Identify key areas that require enhancement. -- Develop a strategic roadmap to advance to higher maturity levels. -- Acquire knowledge about optimal practices, security measures, and key performance indicators. - -## Key Focus Areas for DevOps Maturity Levels - -Experts suggest assessing an organization's DevOps maturity by examining its performance in four key areas: - -### Culture and Strategy -In the DevOps maturity model, culture shapes team collaboration and operations. A teamwork, transparency, and unity culture supports efficient deployment and monitoring. For advanced maturity, the team is supposed to adopt a customer-centric and product-oriented mindset, ensuring all team members align their goals to deliver rapid value. - -### Automation -DevOps automation or AutoDevOps is crucial for continuous delivery and deployment. It simplifies development, testing, and production by automating repetitive tasks, which saves time and improves resource efficiency in the CI/CD process. - -### Structure and Process -In the maturity model in DevOps, the process element involves breaking down work into manageable steps to complete a product's lifecycle. Effective DevOps processes should be standardized and clearly defined to maximize efficiency. Key characteristics of a mature DevOps framework include handling work in small, manageable chunks, maintaining complete transparency of progress, and eliminating unnecessary steps that lead to delays and resource waste. - -### Collaboration and Sharing -Collaboration is a cornerstone of the DevOps model and a key metric of team effectiveness and productivity. Cohesive teams are more likely to optimize processes and develop practical solutions, leveraging diverse skill sets towards a unified objective. - -### Technology -Selecting the appropriate technology is crucial in the DevOps framework. The chosen tools and technologies should align with your team's needs to maximize productivity and effectiveness. Modern tools enable DevOps teams to continuously develop and monitor products, aiming to deliver valuable software to customers swiftly. - -## What Defines a High-Quality DevOps Maturity Model - -- **Assessment Criteria**: Standards used to evaluate the effectiveness and maturity of DevOps practices within an organization. -- **Maturity Levels**: A structured progression of DevOps adoption typically encompasses five stages, though some models may include additional phases. -- **DevOps Practices**: Detailed descriptions of core DevOps techniques including release management, task automation, security protocols, CI/CD, and IaC. -- **Relevant Metrics**: KPIs for evaluating DevOps effectiveness including deployment frequency, MTTR, and change failure rate. -- **Cultural Guides**: Strategies for assessing and enhancing organizational culture to align with DevOps principles. -- **Tools and Technologies**: Version control systems, CI/CD platforms, automation tools, and containerization solutions. -- **Roles and Responsibilities**: Precise definitions of team roles including process ownership, disaster recovery, QA, CI/CD pipeline design, threat response, and system availability. - -## 5 Stages of the DevOps Maturity Model - -### Phase 1: Initial/Ad-Hoc (You Haven't Started DevOps) - -| Aspect | Description | -|--------|-------------| -| Organization | Teams (development, operations, security, product management, and users) work in isolation with different priorities, leading to inefficiencies. | -| Delivery | Waterfall approach, focusing on features and timelines instead of business outcomes. Release cycles based on milestones rather than user feedback or market changes. | -| Automation | Manual infrastructure management is slow and error-prone. Servers receive individual attention instead of being managed in bulk. | -| Testing | Manual testing creates bottlenecks and delays. | -| Security | Security involvement occurs only weeks before release, focusing on minimal compliance scans. | -| Monitoring | Outages are reported by users rather than detected proactively, leading to reactive responses. | -| Operations | Operations teams receive releases with minimal planning, affecting deployment efficiency. | - -### Phase 2: DevOps in Pockets - -| Aspect | Description | -|--------|-------------| -| Organization | Dev and Ops teams work together on small, strategic projects. | -| Delivery | Agile practices are introduced, focusing on business and user value instead of just project planning. | -| Version Control | Version control is used to manage environments and configurations. | -| Automation | Teams use automation to reduce release risks, but some automation is superficial. | -| Testing | Unit, integration, and end-to-end tests are implemented to enhance quality. | -| Security | Security operates separately from the rest of the team for now. | -| Monitoring | Essential monitoring tools alert the team to issues as soon as they affect users. | -| Manual Interventions | Ops staff must manually intervene when issues occur in production. | -| Operations | The operations team stays informed about upcoming releases and looks for improvement opportunities from performance alerts. | - -### Phase 3: Automated and Defined - -| Aspect | Description | -|--------|-------------| -| Organization | Well-defined and standardized processes across Dev and Ops teams. | -| Delivery | Agile practices are increasingly integrated across development, operations, design, and business teams. | -| Automation | Most infrastructure is automated, making provisioning repeatable and reliable, enabling more frequent deployments. | -| Testing | Security scans are incorporated into testing throughout the development process rather than conducted only at deployment. | -| Security | Security becomes involved in design, architecture, and operations discussions. | -| Bundled Releases | Releases often bundle unrelated features into big projects. | -| Technical Debt | Concepts of MVPs and technical debt still need to be prioritized. | -| Operations | The operations team adopts new automation techniques in their practices. | - -### Phase 4: Highly Optimized DevOps - -| Aspect | Description | -|--------|-------------| -| Organization | Ops and development teams work closely with project management and security in product planning. | -| Automation | Immutable infrastructure replaces old servers rather than updating them. Infrastructure and code updates are managed through pipelines. Security updates are incorporated directly into the product development workflow. | -| Testing | Performance and load testing ensure deployments are ready for production scale. | -| Tech Debt and MVPs | Use of MVPs and management of tech debt to speed up releases. | -| Security | Dependency management identifies third-party vulnerabilities before they cause issues. Continuous security monitoring spreads security awareness across the team. | -| Monitoring | Continuous application monitoring tracks the system's overall health for early problem detection and analysis of root causes. | -| Operations | Developers consider operational aspects in documentation, analytics, and standard operating procedures. | - -### Phase 5: Fully Mature DevOps - -| Aspect | Description | -|--------|-------------| -| Organization | Self-sufficient, full-stack teams across business units. | -| Delivery | Multiple deployments per day with high certainty and minimal risk. | -| Automation | Zero human intervention for code changes passing through the pipeline. | -| Testing | Continuous use of real-time data to make informed decisions and optimize processes. | -| Security | Prevent insecure or non-compliant code from reaching production; high-level security integration. | -| Monitoring | Max uptime with no interruptions to customer experience; high collaboration across teams. | -| Operations | Rapid, data-driven decision-making and innovation are encouraged; teams excel in collaboration and experimentation. | - -## Business Benefits of Adopting the Maturity Model in DevOps - -- **Quickier Adjustment to Changes**: CI/CD pipelines enable swift roll-out of new features and maintain operational agility. -- **Capability to Seize Opportunities**: Advanced DevOps practices enable rapid deployment of updates, helping companies enter new markets ahead of competitors. -- **Spot Areas of Satisfaction**: Consistent evaluation of practices helps pinpoint inefficiencies and implement targeted improvements. -- **Better Scalability**: IaC enables automated resource provisioning and management with minimal manual effort. -- **Enhanced Operational Performance**: Automation of repetitive tasks bridges gaps between development and operations teams, reducing manual errors. -- **Faster Delivery Times**: Automated testing, integration, and deployment significantly reduce time-to-market. -- **Improved Quality**: Continuous monitoring and feedback loops enable early detection and resolution of issues. - -## Security Linked With the DevOps Maturity Model - -As organizations advance in their DevOps automation, the need for faster release cycles and digital innovation becomes crucial, intensifying the focus on security. The core of DevOps security is merging development, operations, and security into a unified process — realized through **DevSecOps**, which guarantees that security is woven into every phase of the Software Development Lifecycle. Effective DevSecOps practices involve collaboration between DevOps and security teams, implementing security policies and frameworks across all tools and resources. Solutions like containerization address security issues by minimizing the exposure of vulnerable resources. - -## Most Common Roadblocks That Hold DevOps Maturity Back - -- Poor communication between Dev and Ops teams -- Lack of clear objectives and strategies -- Resistance to change -- Insufficient investments in tools, training, and resources -- Poor governance leading to inconsistent practices -- Inflexible processes and workflows -- Excluding end-users from the improvement project -- Inadequate integration with business processes - -## How To Measure DevOps Maturity - -DevOps maturity metrics include: - -- **Time-To-Market**: Period from initial concept to product launch -- **Lead Time**: Interval from code commitment to deployment -- **Development Frequency**: Rate at which code is deployed within a set period -- **Code Quality**: Code complexity, test coverage, and feedback from code evaluations -- **Code Deployment Success Rate**: Proportion of successful deployments -- **Change Failure Rate**: Proportion of deployments that encounter issues or failures -- **Rollback Rate**: Proportion of deployments that are reverted -- **Error Budget**: Permissible rate of errors and failures in production -- **Availability**: Time the system remains operational and accessible to users -- **Scalability**: System's ability to manage increased load without performance issues -- **Time-in-stage**: Average duration to complete each phase of the development process -- **Code Review Feedback Loop Time**: Time to receive and act on feedback from code reviews -- **MTTR (Mean Time to Recovery)**: Average time to recover from a failure -- **MTTD (Mean Time to Detect)**: Average time to identify a problem -- **MTTA (Mean Time to Acknowledge)**: Average time to acknowledge and begin addressing a problem - -## Related Concepts -- [[concepts/DevOps-Maturity]] — General DevOps maturity assessment -- [[concepts/DORA-Metrics]] — Core DORA metrics for DevOps performance measurement -- [[concepts/DevSecOps]] — Security integration in DevOps -- [[concepts/Continuous-Integration]] — CI practices in DevOps maturity -- [[concepts/Continuous-Deployment]] — CD practices in DevOps maturity -- [[concepts/Lead-Time]] — Lead Time for changes metric -- [[concepts/Time-to-Market]] — Time-to-market metric -- [[concepts/MTTR]] — Mean Time to Recovery -- [[concepts/MTTD]] — Mean Time to Detect -- [[concepts/MTTA]] — Mean Time to Acknowledge -- [[concepts/Change-Failure-Rate]] — Change failure rate metric -- [[concepts/Error-Budget]] — Error budget concept - -## Source References -- This source adds depth to the [[entities/DevOps-Maturity-Model]] entity with detailed Phase 1-5 descriptions -- Complements [[concepts/DevOps-Maturity]] with specific organizational and technical characteristics at each maturity level -- Expands [[concepts/DORA-Metrics]] with additional operational metrics (MTTD, MTTA, Time-to-Market, Rollback Rate, Error Budget, Availability, Scalability) +--- +title: "DevOps Maturity Model From Traditional IT to Advanced DevOps" +type: source +tags: [DevOps, DevOps Maturity, CI/CD, Automation, DevSecOps] +date: 2024-08-14 +--- + +## Source File +- [[Cloud & DevOps/DevOps Maturity Model From Traditional IT to Advanced DevOps]] + +## Summary（用中文描述） +- 核心主题：DevOps 成熟度模型的五阶段演进框架，从传统 IT 到完全成熟的 DevOps +- 问题域：组织如何评估当前 DevOps 实践水平，识别改进领域，制定升级路线图 +- 方法/机制：通过四个核心关注领域（文化与战略、自动化、结构与流程、协作与共享、技术）评估组织 DevOps 成熟度，分为五个递进阶段 +- 结论/价值：DevOps 成熟度模型是组织规划 DevOps 转型路径的结构化工具，涵盖从初始/临时阶段到完全成熟连续部署的全过程，并提供衡量指标和常见障碍识别 + +## Key Claims（用中文描述） +- DevOps 成熟度模型通过四个关键领域评估组织能力：文化与战略、自动化、结构与流程、协作与共享、技术 +- 五阶段成熟度模型依次为：Phase 1 初始/临时阶段 → Phase 2 局部试点 → Phase 3 自动化与定义 → Phase 4 高度优化 → Phase 5 完全成熟 +- 完全成熟的 DevOps 实践实现零人工干预的流水线、每日多次部署、高确定性低风险发布 +- DevOps 成熟度关键衡量指标包括：部署频率、变更前置时间（Lead Time）、平均恢复时间（MTTR）、变更失败率、错误预算（Error Budget） +- DevSecOps 将安全集成到 DevOps 每个阶段，是高级成熟度阶段的核心要求 +- 团队协作是 DevOps 的基石，也是衡量团队效能和生产力的关键指标 + +## Key Quotes +> "The DevOps Maturity Model is a powerful tool for guiding organizations through the evolution of their DevOps practices, from initial adoption to achieving full maturity." — DevOps 成熟度模型的核心定位 +> "DevOps automation or AutoDevOps is crucial for continuous delivery and deployment. It simplifies development, testing, and production by automating repetitive tasks, which saves time and improves resource efficiency in the CI/CD process." — 自动化在 DevOps 中的核心价值 +> "The core of DevOps security is merging development, operations, and security into a unified process." — DevSecOps 的核心理念 + +## Key Concepts +- [[DevOps]]：一种融合开发与运维的文化、实践和技术组合，强调协作、自动化和持续改进 +- [[DevSecOps]]：将安全实践集成到 DevOps 流程的每个阶段（通过 DevOps Maturity Model Phase 4-5 实现） +- [[Continuous Delivery]]：持续交付，使代码变更可随时安全部署到生产环境 +- [[Agile]]：敏捷方法，从 Phase 2 开始引入，强调业务和用户价值而非仅项目规划 +- [[MVP]]：最小可行产品，在 Phase 4 高度优化阶段用于加速发布 +- [[Technical Debt]]：技术债务，在 Phase 3-4 阶段开始被优先管理和处理 +- [[Infrastructure as Code]]（IaC）：基础设施即代码，在 Phase 4 实现不可变基础设施替换旧服务器 +- [[MTTR]]（Mean Time to Recovery）：平均恢复时间，DevOps 成熟度关键衡量指标 +- [[Change Failure Rate]]：变更失败率，DevOps 关键绩效指标之一 +- [[Deployment Frequency]]：部署频率，完全成熟阶段实现每日多次部署 +- [[Lead Time]]：前置时间，从代码提交到部署的时间周期 +- [[concepts/Error-Budget]]：错误预算，允许的生产错误和失败率 +- [[concepts/Immutable-Infrastructure]]：不可变基础设施，在 Phase 4 替换旧服务器而非更新 +- [[Version Control]]：版本控制，从 Phase 2 开始用于管理环境和配置 + +## Key Entities +- [[entities/DevOps-Maturity-Model]]：本文核心——评估和指导 DevOps 转型的五阶段成熟度模型 +- [[DevOps Culture and Transformation]]：DevOps 文化转型相关主题，与本文 Phase 1-2 的文化演进强相关 +- [[Release Management]]：发布管理，涵盖部署频率、变更失败率等关键指标，与本文衡量指标重叠 + +## Connections +- [[DevOps Culture and Transformation]] ← foundational ← [[entities/DevOps-Maturity-Model]] +- [[DevOps]] ← encompasses ← [[entities/DevOps-Maturity-Model]] +- [[DevSecOps]] ← integrates ← [[DevOps]] + Security（本文 Phase 4-5 体现） +- [[Continuous Delivery]] ← supports ← [[entities/DevOps-Maturity-Model]] +- [[Release Management]] ← measures ← DevOps Maturity（共享 Deployment Frequency, Lead Time, MTTR 等指标） +- [[concepts/Error-Budget]] ← part of ← DORA Metrics +- [[concepts/Immutable-Infrastructure]] ← enables ← Phase 4 高度优化 + +## Contradictions +- 与 [[DevOps Culture and Transformation]] 的潜在视角差异： + - 冲突点：文化转型是 DevOps 成功的前提还是结果？ + - 当前观点（本文）：文化是成熟度的一个评估维度，从 Phase 1（孤立文化）到 Phase 5（自足全栈团队） + - 对方观点：文化转型应该是最先启动的变革，需先改变团队协作方式才能推进其他实践 +- 与 [[Waterfall]] 的对比冲突： + - 冲突点：传统瀑布式方法是否完全无法满足现代软件交付需求？ + - 当前观点（本文）：瀑布式是 Phase 1 的典型特征，以里程碑而非用户反馈驱动，是需要淘汰的落后模式 + - 对方观点：瀑布式在稳定需求、长周期硬件项目或合规要求严格的场景中仍有价值 diff --git a/wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md b/wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md index e97be811..b8a27c1c 100644 --- a/wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md +++ b/wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md @@ -1,154 +1,69 @@ ---- -title: How Can a Multi Cloud Strategy Transform Your Business ROI? -source: https://www.bacancytechnology.com/blog/multi-cloud-strategy -author: shenwei -published: 2024-12-24 -created: 2025-03-01 -description: Explore how a multi-cloud strategy can boost performance, reduce risks, and maximize ROI on your cloud investments while ensuring scalability and flexibility. -tags: [Multi-Cloud, Cloud Strategy, ROI, Cloud DevOps] ---- - -# How Can a Multi Cloud Strategy Transform Your Business ROI? - -## Source File -- [[raw/Cloud & DevOps/How Can a Multi Cloud Strategy Transform Your Business ROI.md]] - -## Quick Summary - -This article explores what a multi-cloud strategy is, why it's a game-changer for businesses, and how it addresses key challenges like vendor lock-in, compliance, and performance optimization. The guide covers leveraging strengths of multiple cloud providers, streamlining operations, and reducing risks. - -## Key Statistics - -- **78%** of businesses leveraging multi-cloud have workloads deployed in more than three public clouds (Virtana) -- **86%** of companies intend to adopt multi-cloud by end of 2024 (New Horizons) -- **30%** reduction in operations costs after optimizing resources and negotiating favorable prices (Forrester) - -## What is Multi-Cloud Strategy? - -**Definition**: A distinctive approach using instances of services on multiple clouds (Azure, GCP, AWS) instead of one vendor, allowing businesses to leverage each provider's strengths and unique features. - -**How It Works**: Businesses distribute workloads across providers to access specific services or pricing models without single-provider dependency. - -### Common Misconceptions - -- **Not Just a Backup Strategy**: Multi-cloud is not merely disaster recovery — its true value lies in optimizing performance, cost, and scalability -- **Not Always More Complex**: With right tools (cloud automation, governance frameworks, containerization), multi-cloud strengthens system resilience - -## Why Businesses Adopt Multi-Cloud - -1. **Avoiding Vendor Lock-In** — Pick best cloud services based on costs, performance, or special functions -2. **Increased Resilience and Reliability** — Redundancy across platforms ensures service continuity -3. **Improved Security Posture** — Deploy different security mechanisms within each provider's strong points -4. **Scalability** — Accommodate fluctuating demands with flexible resource allocation -5. **Cost Optimization** — Tap into each provider's cost advantages (one may be cheaper for storage, another for compute) -6. **Access to Innovation** — Stay at forefront with different providers' tools and services -7. **Regulatory Compliance** — Pick providers with region/industry-specific certifications -8. **Performance Optimization** — Select best provider for different workloads (ML vs. analytics) - -## Key Business Challenges Addressed - -1. **Risk Mitigation** — Distribute workloads over multiple clouds to prevent single-provider failure -2. **Cost Optimization** — Get best deals across providers, reduce overhead costs -3. **Data Sovereignty** — Follow global and regional data regulations with compliant storage -4. **Performance** — Optimize for different workload types with superior infrastructure -5. **Complexity Management** — Use multi-cloud management tools for centralized control - -## How Multi-Cloud Maximizes ROI - -### Cost Reduction -- Avoid high single-cloud pricing structures -- Drive hard bargains for better rates -- Prevent paying for unnecessary resources - -### Resource Optimization -- Allocate workloads to best-suited provider (e.g., Google Cloud for ML, AWS/Azure for general infra) - -### Efficiency Gains -- Create tailored cloud architecture -- Reduce downtime, improve performance -- Faster deployment times, better availability - -### Flexibility in Scaling -- Dynamically allocate resources based on demand -- Expand on one provider during traffic spikes without capacity limits -- Avoid overpaying for unused capacity - -### Better Risk Management -- Eliminate single-provider dependency -- Other providers step in when one goes down - -## Real-World Use Cases - -### E-Commerce -- High availability and scalability during peak seasons (Black Friday, Cyber Monday) -- Scale resources across providers for traffic spikes -- Fast customer load times - -### Healthcare -- Keep sensitive patient data secure (HIPAA compliance) -- Distribute data across compliant cloud platforms -- Cut costs from single-cloud dependency - -### Finance -- Secure financial data and protect from regulatory requirements -- Use best security features of different providers -- Reduce risk and vendor lock-in for better SLAs and ROI - -## Implementation Steps - -### Step 1: Assess Your Needs -- Identify goals (resiliency, cost optimization, scale) -- Budget analysis -- Resource requirements assessment - -### Step 2: Choose Right Providers -- Align services with needs (AWS for infra, Google Cloud for analytics, Azure for AI) -- Evaluate features, security, compliance, cost, performance - -### Step 3: Integrate and Manage -- Adopt multi-cloud management tools (Kubernetes, Terraform) -- Ensure data interoperability, avoid data silos - -### Step 4: Monitor and Optimize -- Track resource usage (CloudHealth, Datadog) -- Implement cost-saving measures through workload optimization - -## Challenges and Solutions - -1. **Integration Complexity** - - **Challenge**: Compatibility issues and operational silos - - **Solution**: Use Kubernetes, Terraform, or cloud APIs - -2. **Security Risks** - - **Challenge**: Data breaches and inconsistent policies - - **Solution**: Centralized security protocols, multi-cloud IAM, end-to-end encryption - -3. **Lack of Expertise** - - **Challenge**: Specialized skills may be scarce - - **Solution**: Invest in upskilling, hire experts, or partner with managed providers - -## Related Concepts - -- [[Multi-Cloud-Strategy]] — Updated with ROI maximization framework -- [[Cloud-Maturity-Model]] — Cloud maturity levels for multi-cloud adoption -- [[Cloud-Adoption-Strategy]] — Overall cloud adoption planning -- [[FinOps]] — Cloud financial management -- [[Vendor-Lock-In]] — Risk of single-provider dependency -- [[Data-Sovereignty]] — Regional compliance requirements -- [[Kubernetes]] — Container orchestration for multi-cloud -- [[Terraform]] — Infrastructure as Code for multi-cloud - -## Key Entities - -- [[Cloud Computing]] — Updated with multi-cloud deployment model -- [[AWS]] — Amazon Web Services -- [[Azure]] — Microsoft Azure -- [[Google-Cloud]] — Google Cloud Platform - -## Notes - -This source provides a comprehensive business case for multi-cloud ROI, extending the existing [[Multi-Cloud-Strategy]] concept with: -- Quantified benefits (30% cost reduction, 78% adoption rate) -- Industry-specific use cases (e-commerce, healthcare, finance) -- Practical implementation roadmap (4 steps) -- Real-world challenges with proven solutions +--- +title: "How Can a Multi Cloud Strategy Transform Your Business ROI?" +type: source +tags: [Cloud, Multi-Cloud, ROI, DevOps] +date: 2024-12-24 +--- + +## Source File +- [[Cloud & DevOps/How Can a Multi Cloud Strategy Transform Your Business ROI.md]] + +## Summary（用中文描述） +- 核心主题：多云策略（Multi-Cloud Strategy）的商业价值——如何通过多云架构提升业务 ROI、降低风险、增强弹性 +- 问题域：企业在云迁移和云运营中面临的供应商锁定、成本失控、合规复杂、可用性不足等挑战 +- 方法/机制：跨多个云服务提供商（AWS/Azure/GCP）分配工作负载，利用各提供商优势实现成本优化、弹性扩展和安全增强 +- 结论/价值：78% 企业使用 3+ 公有云；86% 企业计划 2024 年底采用多云；优化后可实现 30% 运营成本降低；多云策略是企业在数字化竞争中保持敏捷的关键 + +## Key Claims（用中文描述） +- 78% 采用多云策略的企业使用 3+ 公有云以提升敏捷性和成本节约（Virtana） +- 86% 企业计划 2024 年底采用多云策略以满足持续业务需求（New Horizons） +- 优化资源和与不同云服务商谈判后，多数企业享受 30% 运营成本降低（Forrester） +- 78% 企业已采用多云策略；平均使用 2-5 个云服务商；多云是主流趋势 + +## Key Quotes +> "The multi cloud strategy is a distinctive approach in which we have instances of services on multiple clouds, i.e., Azure, GCP, and Amazon, instead of one cloud vendor." — Bacancy Technology，核心定义 + +> "A multi-cloud approach will provide businesses with more innovation and ensure they are always at the forefront of this rapidly evolving digital landscape." — Bacancy Technology，多云创新的价值 + +> "After optimizing resources and negotiating favorable prices with different cloud service providers, most companies enjoy a 30% reduction in operations costs." — Forrester，成本优化数据来源 + +## Key Concepts +- [[Multi-Cloud-Strategy]]：使用多个云服务提供商来避免锁定、增强弹性、优化成本，是本文核心主题 +- [[Vendor-Lock-In]]：多云策略的首要动因——企业通过多云摆脱对单一供应商的依赖 +- [[Data-Sovereignty]]：多云策略满足数据主权合规——不同地区选择符合当地法规的云服务商 +- [[High Availability]]：多云跨平台冗余实现 99.99%+ 可用性目标 +- [[Scalability]]：多云弹性扩展能力——跨提供商动态分配资源，应对流量高峰 +- [[Cost Optimization]]：多云实现 30% 运营成本降低——跨提供商比价、优化资源配置 + +## Key Entities +- [[AWS]] — 主要云提供商之一，可用于基础设施和通用计算 +- [[Azure]] — Microsoft Azure，多云策略中用于 AI 工具集成 +- [[Google-Cloud]] — GCP，ML/AI 工作负载的首选提供商 +- Bacancy Technology — 文章原始发布方，提供云托管服务 + +## Connections +- [[Multi-Cloud-Strategy]] ← is_about ← 本文核心主题 +- [[Vendor-Lock-In]] ← solves ← [[Multi-Cloud-Strategy]] 的首要动机 +- [[Data-Sovereignty]] ← enables ← [[Multi-Cloud-Strategy]] 的合规能力 +- [[High Availability]] ← achieved_by ← [[Multi-Cloud-Strategy]] 跨云冗余 +- [[Cloud-Operating-Model]] ← includes ← [[Multi-Cloud-Strategy]] 作为核心组件 +- [[Cloud-Governance]] ← governs ← [[Multi-Cloud-Strategy]] 的实施 +- [[FinOps]] ← optimizes ← [[Multi-Cloud-Strategy]] 的成本管理 + +## Real-World Use Cases（原文关键案例） +- **电商**：黑色星期五/网络星期一等高峰期跨多云弹性扩展，保障高可用和快速加载 +- **医疗**：符合 HIPAA 保护患者数据，符合区域数据主权要求，降低单一云依赖成本 +- **金融**：利用不同云最佳安全功能，满足严格监管要求，减少供应商锁定，获得更好 SLA + +## Implementation Framework（原文实施路径） +1. **评估需求**：明确目标（弹性/成本/规模）、预算分析、资源评估 +2. **选择提供商**：对齐服务与需求（如 AWS 基础设施、GCP 分析、Azure AI） +3. **集成管理**：采用 Kubernetes/Terraform 等多云管理工具，确保数据互操作性 +4. **监控优化**：使用 CloudHealth/Datadog 持续监控性能和成本 + +## Contradictions +- 与 [[cloud-operating-model-key-strategies-and-best-practices]] 中的"统一云治理"观点存在潜在张力： + - 冲突点：多云策略天然带来管理复杂性 + - 当前观点（本文）：多云管理工具（Kubernetes/Terraform）可简化复杂性 + - 对方观点：需要统一的 Cloud Operating Model 治理框架来协调多云环境 + - 协调方向：两者互补——多云策略是选择层，Cloud Operating Model 是治理层 diff --git a/wiki/sources/public-vs-private-vs-hybrid-cloud-differences-explained.md b/wiki/sources/public-vs-private-vs-hybrid-cloud-differences-explained.md index d5b84cec..73f8479b 100644 --- a/wiki/sources/public-vs-private-vs-hybrid-cloud-differences-explained.md +++ b/wiki/sources/public-vs-private-vs-hybrid-cloud-differences-explained.md @@ -1,61 +1,59 @@ ---- -title: "Public vs Private vs Hybrid Cloud Differences Explained" -type: source -tags: [] -date: 2025-06-18 ---- - -## Source File -- [[raw/Cloud & DevOps/Public vs Private vs Hybrid Cloud Differences Explained.md]] - -## Summary (中文) -- **核心主题**：公有云、私有云、混合云三种云部署模型的定义、优缺点、适用场景及选择决策框架 -- **问题域**：云部署策略选择；成本 vs 安全 vs 性能 vs 可扩展性的权衡 -- **方法/机制**：三种云模型的结构化对比；共享责任模型；混合云的同构/异构决策 -- **结论/价值**：云部署选择没有标准答案，需根据工作负载特点、预算、IT能力制定有意的云策略（intentional cloud strategy），且需持续平衡调整 - -## Key Claims (中文) -- 公有云通过多租户共享模式提供弹性扩展能力，但缺乏成本控制（大规模使用时TCO指数增长）和安全控制 -- 私有云提供独占环境带来更高性能和安全性，适合受监管行业和敏感数据，但TCO高且远程访问受限 -- 混合云通过在公私之间按策略分配工作负载，实现安全与弹性的平衡，但引入成本管理和集成的复杂性 -- 无论选择哪种云模型，云安全问题（访问控制、加密、灾难恢复）始终由用户组织与供应商共同承担——即"共享责任模型" - -## Key Quotes - -> "The rapid switch from local to cloud computing is driven by benefits such as the ability to scale without having to buy and configure hardware, accessibility from anywhere with an internet connection, professionally managed servers that are kept up-to-date with the latest tech and versions of apps, cost efficiency, and quick recovery from cyber attacks." — 云采用的核心驱动因素概述 - -> "The choice between public vs private vs hybrid cloud solutions depends on your use cases, budget, IT capabilities, and expectations for growth. It is rarely an either/or situation, as you may find ways to capture the benefits of each while avoiding the drawbacks." — 云部署选择的核心洞察 - -> "It is important to know that no matter which cloud environment you work in, your problems don't go away... your organization maintains responsibility for: Who has access to what, Cloud security and encryption, Disaster recovery planning." — 共享责任模型的核心 - -## Key Concepts - -- [[Public Cloud]]：通过互联网交付、多租户共享的云服务模式（AWS、Azure、GCP） -- [[Private Cloud]]：专属于单一组织的云环境，通过私有网络访问，可本地托管或第三方托管 -- [[Hybrid Cloud]]：同时使用公有云和私有云的混合环境，在两者之间按策略分配工作负载 -- [[Shared Responsibility Model]]：云安全由供应商和组织共同承担的安全责任划分模型 -- [[Cloud Elasticity]]：云环境快速扩展或收缩资源的能力，无需硬件采购和配置 -- [[CapEx-vs-OpEx]]：资本支出（前期硬件投入）与运营支出（按需付费）的对比 -- [[Cost Agility]]：根据业务需求灵活调整云资源消耗以控制成本的能力 -- [[SLA]]：服务级别协议，定义云服务可用性和性能保证 -- [[Disaster Recovery Planning]]：灾难恢复规划，云环境下的业务连续性保障 - -## Key Entities - -- [[BMC]]：BMC Software — 企业IT管理解决方案提供商，文章原出处 -- [[BMC Helix]]：BMC 旗下AI运维平台，帮助IT组织将AI转化为行动 - -## Connections - -- [[Public Cloud]] ← depends_on ← [[Cloud Infrastructure]] -- [[Private Cloud]] ← depends_on ← [[Cloud Infrastructure]] -- [[Hybrid Cloud]] ← combines ← [[Public Cloud]] AND [[Private Cloud]] -- [[Cloud Adoption Strategy]] ← informs ← [[Public Cloud]] / [[Private Cloud]] / [[Hybrid Cloud]] 选择 -- [[FinOps]] ← constrains ← [[Cost Agility]] -- [[Shared Responsibility Model]] ← applies_to ← ALL three cloud models -- [[SLA]] ← guarantees ← [[High Availability]] -- [[Multi-Cloud Strategy]] ← related_to ← [[Hybrid Cloud]]（有重叠但不同） - -## Contradictions - -- **公有云安全 vs 私有云安全**：文章认为"公有云安全性最低（least secure）"，但[[Cloud Computing]] entity页面引用的Myth 1真相认为"云比本地更安全"。当前观点：两者描述的角度不同——本文从多租户共享模型角度认为公有云安全性最低；Myth 1从整体云安全投入（加密、MFA、ISO 27001）角度认为云比本地安全。两者均为有效视角，安全最终取决于具体实现而非部署模型本身。 +--- +title: "Public vs Private vs Hybrid Cloud Differences Explained" +type: source +tags: [cloud-computing, cloud-strategy, infrastructure] +date: 2025-06-18 +--- + +## Source File +- [[Cloud & DevOps/Public vs Private vs Hybrid Cloud Differences Explained]] + +## Summary（用中文描述） +- **核心主题：** 公有云、私有云与混合云三种云计算部署模型的核心差异、优缺点及适用场景对比 +- **问题域：** 企业如何根据安全、成本、可扩展性、合规等需求选择合适的云部署模式 +- **方法/机制：** 系统性地从定义、优势、劣势、适用场景四个维度对比三种云模型；强调混合云作为折中方案的价值；提出"共享责任模型"概念 +- **结论/价值：** 三种云模型各有优劣，企业应根据工作负载特点制定有意图（intentional）的云策略，而非简单选择某一模型 + +## Key Claims（用中文描述） +- **公有云** 通过多租户共享模式提供高弹性、低成本、快速上线的计算服务，但在大规模企业场景下 TCO 可能指数级上升，且安全性和合规控制最弱 +- **私有云** 为单一组织提供专用环境，带来更高的安全性、控制力和合规灵活性，但成本最高、管理复杂、对远程用户不够友好 +- **混合云** 通过在同一架构中组合公私云实现"安全与扩展兼得"——敏感工作负载在私有云，普通负载在公有云，兼顾成本效率与安全韧性 +- **云选择决策** 应以工作负载需求为驱动，基于安全性、性能、成本三大维度制定有意图的云策略，且需持续评估和调整 + +## Key Quotes +> "The public cloud is the shared cloud. In this model, third-party providers deliver storage, computing power, and applications to multiple users." — 公有云的定义：第三方提供商向多用户交付共享资源 + +> "The private cloud is dedicated to your organization, which you access over a secure private network." — 私有云的定义：组织专用的安全私有网络访问环境 + +> "The hybrid cloud is a computing environment that uses both the public and private cloud models, sharing data and apps between the two to take advantage of the benefits that each provides." — 混合云的定义：融合两种模型，通过数据和应用在两者间的共享实现优势互补 + +> "No matter which cloud environment you work in, your problems don't go away. Though you're purchasing services from third-party vendors, you still have to do your due diligence." — 共享责任模型：无论哪种云环境，用户组织仍需对访问控制、云安全和灾难恢复承担最终责任 + +## Key Concepts +- [[CloudComputing]]：通过互联网远程使用第三方服务器上的计算资源，无需本地部署硬件 +- [[PublicCloud]]：多租户共享模式，第三方提供商向多个组织交付存储、计算能力和应用，按用量付费 +- [[PrivateCloud]]：单一组织专用的云环境，通过安全私有网络访问，可本地托管或第三方管理，提供更高安全性、控制力和合规性 +- [[HybridCloud]]：同时使用公有云和私有云的计算环境，数据和应用在两者间共享，根据安全、性能、成本需求分配工作负载 +- [[SaaS-PaaS-IaaS]]：云计算服务交付模式的三层——软件即服务、平台即服务、基础设施即服务 +- [[SharedResponsibilityModel]]：云安全责任分配模型——供应商负责底层基础设施灵活性与敏捷性，用户组织负责访问控制、安全加密和灾难恢复规划 +- [[CloudStrategy]]：有意图的云战略——从工作负载需求出发，权衡公私混合各模型利弊，制定并持续调整的云部署策略 + +## Key Entities +- [[BMC]]：BMC Software — 源文章的发布机构，全球企业软件公司，为 Forbes Global 50 中 86% 的企业提供自动化应用、系统和服务 +- BMC Helix：独立运营的公司，帮助企业将 AI 转化为行动 +- RaaS（Ransomware as a Service）：勒索软件即服务——网络犯罪分子利用云基础设施的"犯罪即服务"模式 + +## Connections +- [[PublicCloud]] ← extends ← [[CloudComputing]] +- [[PrivateCloud]] ← extends ← [[CloudComputing]] +- [[HybridCloud]] ← extends ← [[CloudComputing]] +- [[HybridCloud]] ← combines ← [[PublicCloud]] + [[PrivateCloud]] +- [[CloudStrategy]] ← drives ← [[PublicCloud]] + [[PrivateCloud]] + [[HybridCloud]] +- [[SharedResponsibilityModel]] ← applies_to ← [[PublicCloud]] + [[PrivateCloud]] + [[HybridCloud]] +- [[SaaS-PaaS-IaaS]] ← delivered_by ← [[PublicCloud]] + [[PrivateCloud]] + +## Contradictions +- 与 [[CloudComputing]]（来源：[[cloud-maturity-model]]）可能存在视角冲突： + - **冲突点：** 本文强调"云消除了基础设施管理复杂性"，而云成熟度模型强调云迁移后运维复杂性的增加 + - **当前观点：** 公有云"减少复杂度"——供应商负责维护最新硬件和应用版本，降低内部 IT 专业知识需求 + - **对方观点：** 实际云迁移会增加运维复杂度——多租户安全治理、成本追踪、跨环境集成等问题需要专门的云运维能力 diff --git a/wiki/sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md b/wiki/sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md index b75c3300..847d1dc4 100644 --- a/wiki/sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md +++ b/wiki/sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md @@ -1,89 +1,73 @@ ---- -title: "RTO vs RPO: Key Differences for Modern Disaster Recovery" -type: source -tags: [cloud, devops, disaster-recovery, feature-flags, continuous-delivery] -date: 2025-07-26 ---- - -## Source File -- [[raw/Cloud & DevOps/RTO vs RPO Key Differences for Modern Disaster Recovery.md]] - -## Summary (用中文描述) -- **核心主题**：现代持续交付场景下 RTO（恢复时间目标）和 RPO（恢复点目标）的区别，以及 Feature Flag 如何实现秒级恢复 -- **问题域**：传统灾备只关注硬件故障，而现代软件交付的最大风险来自代码变更本身 -- **方法/机制**： - - RTO 衡量系统停机时间，RPO 衡量数据丢失量 - - Feature Flag 将部署与发布解耦，支持微恢复（feature 级别回滚） - - Kill Switch 实现配置级热切换，无需重新部署 - - Progressive Rollout 通过分阶段放量控制影响范围 -- **结论/价值**：预防优于恢复；Feature Flag 工具（如 LaunchDarkly）可实现秒级 RTO、近零 RPO，远比传统灾备基础设施性价比高 - -## Key Claims (用中文描述) -- Feature Flag 将部署（deploy）与发布（release）解耦，实现配置级热修复 → RTO 从小时降至秒级 -- 渐进式放量（Progressive Rollout）将影响范围限制在 1% 用户 → 包含损害，RTO 以秒计 -- Kill Switch 支持支付网关、搜索算法、AI 模型等任意组件的热切换 → 无需重新部署代码 -- Feature Flag 回滚不丢失数据（只切换代码路径） → RPO 始终保持近零 -- 传统灾备规划关注硬件故障，但现代交付中代码变更频率更高、风险更大 -- 应用分层级保护（Tier 1/2/3），而非对所有系统一刀切 Tier 1 -- HP 将回滚时间从小时缩短到分钟，Christian Dior 从 15 分钟降至即时切换 - -## Key Quotes -> "RTO is about getting back online. It's the clock that starts ticking the moment your system goes down." — RTO 的本质是系统下线那一刻开始的倒计时 -> "RPO is about protecting data. It's measured backwards from the moment of failure." — RPO 从故障时刻向后追溯可接受的数据丢失窗口 -> "Deploy whenever you want, release when you're ready." — Feature Flag 的核心理念：部署与发布分离 -> "Prevention beats cure." — 预防优于恢复，减少故障比快速恢复更有价值 -> "Your RTO drops to seconds because fixing issues becomes a configuration change, not a code deployment." — Feature Flag 将修复变成配置变更而非代码部署 -> "86% of surveyed LaunchDarkly customers recover from incidents within a day." — LaunchDarkly 客户事故恢复数据 - -## Key Concepts -- [[RTO]]：Recovery Time Objective，系统可容忍的最大停机时间，衡量恢复速度 -- [[RPO]]：Recovery Point Objective，可接受的最大数据丢失量，衡量数据保护程度 -- [[Feature Flag]]：功能开关，将代码部署与功能发布解耦，支持热切换 -- [[Kill Switch]]：应急切断开关，紧急情况下绕过故障组件的机制 -- [[Progressive Rollout]]：渐进式放量，分阶段向用户群发布新功能 -- [[Micro-Recovery]]：feature 级别细粒度恢复，无需回滚整个部署 -- [[Deployment-vs-Release]]：部署（代码到达生产）与发布（用户可见）的分离 -- [[Business Impact Analysis]]：业务影响分析，用于确定不同应用的分层保护级别 - -## Key Entities -- [[LaunchDarkly]]：Feature Flag 管理平台，HP、Christian Dior 等企业的 RTO/RPO 优化案例 -- [[Veeam]]：传统灾备工具（数据库备份、服务器镜像） -- [[Acronis]]：传统灾备工具（跨区域复制） -- [[HP]]：HP 案例——Feature Flag 将回滚时间从小时缩短到分钟 -- [[Christian Dior]]：Christian Dior 案例——回滚从 15 分钟降至即时切换 - -## Connections -- [[Disaster Recovery]] ← extends ← [[RTO]] + [[RPO]]（RTO/RPO 是灾备的核心指标） -- [[Deployment-Automation]] ← depends_on ← [[Feature Flag]]（Feature Flag 是现代部署自动化的基础设施） -- [[CI-CD-Pipeline]] ← extends ← [[Deployment-vs-Release]]（持续交付中的部署与发布分离） -- [[High Availability]] ← depends_on ← [[Kill Switch]]（Kill Switch 是 HA 的应急保障机制） -- [[LaunchDarkly]] ← implements ← [[Feature Flag]]（LaunchDarkly 是 Feature Flag 的商业实现） -- [[Feature Flag]] ← enables ← [[Progressive Rollout]]（Feature Flag 支持渐进式放量） - -## Contradictions -- 与传统灾备观点冲突： - - **冲突点**：传统灾备投资（热备服务器、跨区域复制）vs Feature Flag 方案 - - **当前观点**（本文）：软件优先方法（Feature Flag + Kill Switch）ROI 更高；HP 案例显示 8% 客户运维成本降低超 50% - - **对方观点**（传统 DR）：关键业务系统需要完整的基础设施冗余（Active-Active、跨区域热备） - -## Tiering Reference Table - -| Tier | 场景 | RTO 目标 | RPO 目标 | 投资策略 | -|------|------|----------|----------|----------| -| (1) Critical | 支付处理、用户认证 | < 5 分钟 | < 1 分钟 | Feature Flag + 自动化监控 + 3AM 告警 | -| (2) Important | 管理后台、报表 | < 1 小时 | < 15 分钟 | Feature Flag（主要发布）+ 业务时间监控 | -| (3) Nice-to-have | 内部工具、文档站 | < 4 小时 | < 1 小时 | 基础监控 + 手动恢复流程 | - -## Application Criticality Questions - -**If down for an hour:** -- Lost revenue? How much? -- Angry customers? How many? -- Blocked employees? Can they work around it? -- Regulatory issues? Legal problems? - -**If losing last hour of data:** -- Can we recreate it? -- Does it contain money/transactions? -- Will users notice? -- Is it required for compliance? +--- +title: "RTO vs RPO: Key Differences for Modern Disaster Recovery" +type: source +tags: [cloud-devops, disaster-recovery, sre, feature-flags, continuous-delivery] +date: 2019-01-18 +--- + +## Source File +- [[Cloud & DevOps/RTO vs RPO Key Differences for Modern Disaster Recovery]] + +## Summary（用中文描述） +- 核心主题：RTO（Recovery Time Objective）和 RPO（Recovery Point Objective）在现代灾难恢复和持续交付中的关键区别与实践应用 +- 问题域：云原生/DevOps 环境下的灾难恢复规划、软件部署风险管控、Feature Flag 驱动的微恢复策略 +- 方法/机制： + - RTO 衡量系统停机时长容忍度，RPO 衡量数据丢失容忍度 + - 应用分层（Tier 1/2/3）分配差异化恢复目标 + - Feature Flag 实现部署与发布解耦，支持渐进式灰度发布和即时 Kill Switch + - Feature Flag 将 RTO 从"小时级回滚"缩短至"秒级开关切换" +- 结论/价值：预防优于恢复；Feature Flag 是现代持续交付中实现激进 RTO/RPO 目标的最佳投资回报比方案 + +## Key Claims（用中文描述） +- Feature Flag 将部署（Deploy）与发布（Release）解耦，使回滚从"紧急代码部署（小时级）"变为"配置变更（秒级）" +- 渐进式灰度发布（1%→5%→25%→100%）将故障影响范围限制在早期阶段，RTO 可降至秒级 +- 不能单独优化 RTO 或 RPO——高频备份（优秀 RPO）+ 慢速恢复（糟糕 RTO）等于无用功 +- 不同的应用/功能应拥有不同的恢复目标（Core Payment: 秒级 RTO + 零 RPO；Beta 功能: 分钟级 RTO） +- 成本效益原则：若停机一小时损失 $10K，不要每年花 $100K 基础设施去预防它 + +## Key Quotes +> "RTO is about speed: how fast you get back online. RPO is about data: how much you can afford to lose." — 核心概念区分 +> "Deploy whenever you want, release when you're ready." — Feature Flag 解耦哲学 +> "Having backups every 30 seconds (a great RPO) doesn't help if it takes you 6 hours to restore from those backups (a terrible RTO)." — RTO/RPO 必须同时优化 +> "Prevention beats cure: the best disaster recovery solution is the one you'll actually use when things go wrong." — HP 案例引出核心结论 + +## Key Concepts +- [[概念页面待创建]]：**RTO（Recovery Time Objective）**——系统允许的最大停机时长，从故障发生时刻开始计时 +- [[概念页面待创建]]：**RPO（Recovery Point Objective）**——允许丢失的最大数据量，从上一备份时刻向前测量 +- [[概念页面待创建]]：**Feature Flag**——通过条件分支控制功能上线，无需重新部署即可启用/禁用功能 +- [[概念页面待创建]]：**Kill Switch**——紧急禁用故障功能的即时开关，Feature Flag 驱动的 RTO 保险机制 +- [[概念页面待创建]]：**Progressive Rollout**——渐进式功能发布（1%/5%/25%/100%），限制故障影响范围 +- [[概念页面待创建]]：**Micro-Recovery**——基于 Feature Flag 的功能级回滚，而非整应用回滚 + +## Key Entities +- [[实体页面待创建]]：**LaunchDarkly**——Feature Flag 管理平台，本文档的主要案例引用来源（HP、Christian Dior 等案例） +- [[实体页面待创建]]：**Veeam / Acronis**——传统 DR 工具（备份/服务器镜像/跨区域复制），作为传统方案对照组 + +## Connections +- [[what-i-know-about-cloud-service-delivery-1]] ← 包含 ← [[rto-vs-rpo-key-differences-for-modern-disaster-recovery]]（本文档是云服务交付"备份恢复与灾难管理"领域的具体展开） +- [[devops-maturity-model-from-traditional-it-to-advanced-devops]] ← 支撑 ← [[rto-vs-rpo-key-differences-for-modern-disaster-recovery]]（DevOps 成熟度中"监控可观测性"和"错误预算"是 RTO/RPO 的量化手段） +- [[cloud-devop-maturity-guideline]] ← 关联 ← [[rto-vs-rpo-key-differences-for-modern-disaster-recovery]]（DORA 四项指标中的 MTTR 直接对应 RTO） +- [[continuous-delivery]]（概念尚待建立）← 核心应用场景 ← [[rto-vs-rpo-key-differences-for-modern-disaster-recovery]] + +## Contradictions +- 与传统 DR 思维存在框架冲突： + - 冲突点：传统 DR 关注硬件灾难（火灾/断电/硬件故障），本文档认为现代高频部署场景下软件故障（Bug/错误迁移/AI 模型异常）才是主要风险 + - 当前观点：Feature Flag + Kill Switch + 渐进式发布比传统热备基础设施更有效且成本更低 + - 对方观点：传统 DR 基础设施（Veeam/Acronis + 多数据中心热备）仍是不可替代的硬件级保障 + - 注：两者并不互斥——软件层面用 Feature Flag 快速止血，基础设施层面仍需传统 DR 兜底 + +## Tier System Reference（应用分级体系） + +| Tier | 示例 | RTO 目标 | RPO 目标 | 策略 | +|------|------|---------|---------|------| +| (1) Critical | 支付处理、用户认证、核心产品 | < 5 分钟 | < 1 分钟 | Feature Flag + 自动回滚 + 24/7 告警 | +| (2) Important | 管理后台、报表、客户支持工具 | < 1 小时 | < 15 分钟 | Feature Flag + 手动回滚 + 工作时间监控 | +| (3) Nice-to-have | 内部工具、开发环境、文档站 | < 4 小时 | < 1 小时 | 基础监控 + 人工恢复流程 | + +## LaunchDarkly Business Impact Data +- HP：将回滚时间从"小时级"缩短至"分钟级" +- Christian Dior：将 15 分钟回滚缩短为"即时开关切换" +- 86% 的 LaunchDarkly 客户在一天内从故障中恢复 +- 42% 的 LaunchDarkly 客户在"小时级（甚至分钟级）"内恢复 +- 8% 客户运营成本降低超过 50% +- 59% 客户运营成本降低 11%-50% diff --git a/wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md b/wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md index f3bb89de..3fa19bbc 100644 --- a/wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md +++ b/wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md @@ -1,75 +1,58 @@ ---- -title: "The Myths and Misconceptions About Cloud Computing | LinkedIn" -type: source -tags: [cloud-computing, myths, misconceptions, cloud-migration] -date: 2025-03-02 ---- - -## Source File -- [[raw/Cloud & DevOps/The Myths and Misconceptions About Cloud Computing LinkedIn.md]] - -## Summary (中文描述) -- **核心主题**：云计算领域常见的七大误解与真相，澄清企业和个人对云安全、成本、控制权、适用性、迁移复杂性及可靠性的认知误区。 -- **问题域**：云计算认知偏差、安全焦虑、成本管理、数据主权、技术门槛、性能预期。 -- **方法/机制**：通过逐一反驳误区，提供云服务商的安全投入、架构设计、计费模式、治理工具等实证依据。 -- **结论/价值**：破除误解后，企业和个人可以更理性地评估和采用云技术，推动业务效率和创新。 - -## Key Claims (中文描述) -- 云安全机制（加密、防火墙、MFA）+ 合规认证（ISO 27001、HIPAA、GDPR）+ 自动化监控，使云安全优于传统本地部署。 -- 云不是"别人的电脑"，而是覆盖冗余、自动故障转移和高可用性设计的大规模数据中心网络。 -- 按需付费（Pay-as-you-go）+ 预留实例 + 自动扩缩容 + 无服务器计算，可显著降低总拥有成本。 -- 云平台提供完善的权限管理、数据加密和访问日志监控，企业对数据拥有完全控制权。 -- 云服务对小微企业（SMB）和初创企业同样友好，支持灵活定价和企业级技术。 -- 阶段式迁移、混合云方案和专业迁移服务可以有效降低云迁移的复杂性和风险。 -- 主流云服务商 SLA 保障 99.99% 可用性，全球数据中心分布和冗余架构确保高可靠性。 - -## Key Quotes -> "One of the biggest misconceptions about cloud computing is that it is inherently insecure. In reality, leading cloud providers invest heavily in security measures, including encryption, firewalls, and multi-factor authentication." — 安全误解的典型论点 - -> "While it is true that cloud services rely on remote servers, they are far more than just 'someone else's computer.' Cloud providers operate highly sophisticated data centers with redundancy, scalability, and high availability." — "云即他者之电脑"误解的澄清 - -> "Cloud computing follows a pay-as-you-go model, allowing businesses to scale resources as needed." — 按需付费模式核心定义 - -> "major cloud providers offer service-level agreements (SLAs) that guarantee uptime, often exceeding 99.99%" — SLA 可用性保障 - -## Key Concepts -- [[cloud-computing]]：通过互联网按需提供计算资源（服务器、存储、数据库、网络等），无需本地维护。 -- [[Pay-as-you-go]]：按使用量付费的计费模式，是云计算的核心经济模型。 -- [[cloud-security]]：云环境下的安全实践，包括加密、MFA、防火墙、合规认证和 24/7 监控。 -- [[Data-Governance]]：云平台提供的权限管理、数据加密和访问日志监控能力。 -- [[High-Availability]]：通过冗余基础设施和自动化故障转移实现的高可用性架构。 -- [[Failover]]：主系统故障时自动切换到备用系统的机制。 -- [[SLA]]：服务等级协议，云服务商对可用性的正式承诺（如 99.99% uptime）。 -- [[cloud-migration]]：将工作负载从本地迁移到云端的过程，需合理规划以降低风险。 -- [[Cost-Optimization]]：通过预留实例、自动扩缩容和无服务器计算降低云支出。 -- [[Multi-factor-Authentication]]：多因素认证，云安全的基础机制之一。 -- [[Scalability]]：云平台根据负载动态扩展资源的能力。 - -## Key Entities -- [[ISO-27001]]：国际信息安全管理体系标准，云服务商合规认证之一。 -- [[HIPAA]]：美国健康信息隐私法规，云服务商合规认证之一（医疗行业）。 -- [[GDPR]]：欧盟通用数据保护条例，云服务商合规认证之一。 -- [[AWS]]：亚马逊云科技，主流云服务商之一。 -- [[Azure]]：微软云平台，主流云服务商之一。 -- [[Google-Cloud]]：谷歌云平台，主流云服务商之一。 -- [[Raj-Vardhan-Singh]]：本文作者（LinkedIn 发布）。 - -## Connections -- [[cloud-computing]] ← foundational_for ← [[cloud-migration]] -- [[cloud-computing]] ← requires ← [[cloud-security]] -- [[cloud-computing]] ← enabled_by ← [[High-Availability]] -- [[cloud-computing]] ← enabled_by ← [[Scalability]] -- [[cloud-computing]] ← enabled_by ← [[Cost-Optimization]] -- [[cloud-security]] ← enforced_by ← [[ISO-27001]] -- [[cloud-security]] ← enforced_by ← [[HIPAA]] -- [[cloud-security]] ← enforced_by ← [[GDPR]] -- [[cloud-computing]] ← supported_by ← [[AWS]] -- [[cloud-computing]] ← supported_by ← [[Azure]] -- [[cloud-computing]] ← supported_by ← [[Google-Cloud]] -- [[cloud-migration]] ← requires ← [[Failover]] -- [[cloud-computing]] ← governed_by ← [[SLA]] -- [[Pay-as-you-go]] ← enables ← [[Cost-Optimization]] - -## Contradictions -- 与 [[on-premises]] 的对比：本文认为云在安全、成本、控制方面优于本地部署，与某些企业 IT 保守派观点（"数据必须留在本地"）存在冲突。该冲突集中在数据主权和合规要求层面，非技术能力层面。 -- 与传统采购模式对比：本文主张 Pay-as-you-go 更经济，但未提及长期运行稳定工作负载时预留实例的复杂性，以及超大规模迁移初期的隐性成本（ egress 流量、数据传输费用）。 +--- +title: "The Myths and Misconceptions About Cloud Computing | LinkedIn" +type: source +tags: [cloud-computing, misconceptions, cloud-security, cost-optimization] +date: 2025-03-02 +--- + +## Source File +- [[Cloud & DevOps/The Myths and Misconceptions About Cloud Computing LinkedIn]] + +## Summary（用中文描述） +- 核心主题：云计算领域的7大常见误解及其真相 +- 问题域：企业或个人在采用云计算时的认知误区 +- 方法/机制：通过逐一反驳误解，揭示云计算的实际能力与优势 +- 结论/价值：帮助决策者消除顾虑，正确认识云计算的安全性、成本效益和可靠性 + +## Key Claims（用中文描述） +- 云安全往往比本地解决方案更强大：主流云服务商投入大量资源于加密、防火墙、多因素认证，符合 ISO 27001、HIPAA、GDPR 等严苛标准 +- 云远不止是"别人的电脑"：云是由冗余、可扩展、高可用的数据中心网络组成，远超典型本地解决方案 +- 通过适当管理，云计算具有成本效益：采用按需付费模式、预留实例、自动扩展和无服务器计算可显著降低成本 +- 云服务提供强大的数据治理工具：组织可管理权限、加密数据、监控访问日志，支持混合云和多云部署 +- 各类规模的企业都能从云计算中受益：中小企业可享受灵活定价，无需大额前期投资即可使用企业级技术 +- 适当的规划可使云迁移顺利推进：分阶段迁移、混合云方案和专业迁移服务可降低风险 +- 主要云服务商提供高可用性和冗余：SLA 保证可用性通常超过 99.99% + +## Key Quotes +> "Leading cloud providers invest heavily in security measures, including encryption, firewalls, and multi-factor authentication." — 云服务商在安全措施上的持续投入 + +> "Cloud computing follows a pay-as-you-go model, allowing businesses to scale resources as needed." — 按需付费的灵活性 + +> "Major cloud providers offer service-level agreements (SLAs) that guarantee uptime, often exceeding 99.99%." — 服务等级协议保证高可用性 + +## Key Concepts +- [[CloudComputing]]：通过互联网按需提供计算资源、存储和应用的服务模式 +- [[CloudSecurity]]：云环境下的安全实践，包括加密、MFA、安全合规认证 +- [[PayAsYouGo]]：按使用量付费的成本模型 +- [[HybridCloud]]：混合云，结合本地设施和公有云的部署模式 +- [[MultiCloud]]：多云战略，使用多个云服务商的服务 +- [[CloudMigration]]：将工作负载从本地迁移到云端的过程 +- [[HighAvailability]]：高可用性设计，确保服务持续运行 +- [[AutoScaling]]：根据负载自动调整资源的能力 + +## Key Entities +- [[ISO27001]]：国际认可的信息安全管理标准 +- [[HIPAA]]：美国医疗保健信息保护法规 +- [[GDPR]]：欧盟通用数据保护条例 + +## Connections +- [[CloudComputing]] ← topic ← [[The Myths and Misconceptions About Cloud Computing]] +- [[CloudSecurity]] ← key_mechanism ← [[CloudComputing]] +- [[PayAsYouGo]] ← cost_model ← [[CloudComputing]] +- [[HybridCloud]] ← solution_type ← [[CloudMigration]] + +## Contradictions +- 与 On-Premises 相比的误解： + - 冲突点：安全性、控制权、可靠性 + - 当前观点：云安全更强（专业团队 24/7 监控、自动更新）、数据控制完善、高可用 SLA + - 对方观点：本地部署更安全、更可控、性能更稳定 diff --git a/wiki/sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md b/wiki/sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md index fe912232..27e238de 100644 --- a/wiki/sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md +++ b/wiki/sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md @@ -1,63 +1,54 @@ ---- -title: "These 6 Linux Apps Let You Monitor System Resources in Style" -type: source -tags: [linux, system-monitoring, devops-tools, open-source] -date: 2025-12-18 ---- - -## Source File -- [[raw/Cloud & DevOps/These 6 Linux apps let you monitor system resources in style.md]] - -## Summary (中文描述) -- **核心主题**：介绍6款Linux系统资源监控工具，涵盖TUI（文本界面）和GUI两大类 -- **问题域**：Linux系统监控、进程管理、性能分析 -- **方法/机制**： - - TUI工具：Btop++（综合最强）、Htop（轻量）、Glances（超轻）、Bottom（图表为主） - - GUI工具：Mission Center（类Windows任务管理器）、Stacer（功能最全） -- **结论/价值**：作者首推Btop++，兼具美观与实用；需要GUI则选Mission Center或Stacer - -## Key Claims (中文描述) -- **Btop++** 通过提供CPU/内存/网络/存储实时面板、交互式进程管理（f搜索、t终止、k强杀、Nice值调整）成为作者最爱 -- **Htop** 以极简键盘驱动（F3搜索、F9终止、F7/F8调整优先级）提供轻量级进程监控 -- **Glances** 以纯键盘驱动和超轻量特性，适合SSH远程访问场景 -- **Bottom** 专注实时性能图表绘制，不提供交互式进程管理 -- **Mission Center** 以类Windows任务管理器的图形界面（性能/应用/服务三标签）提供友好体验 -- **Stacer** 提供最全面的功能集（监控+启动项管理+包卸载+GNOME设置+缓存清理） - -## Key Quotes -> "TUI apps make the best resource monitors — they're snappy and responsive, even when the GUI is lagging." — 作者偏好TUI工具的核心原因 -> "Btop++ always gets my vote. It features a nice balance between usability and aesthetics." — 作者最终推荐 -> "Mission Center is your friend" if you want something close to the Windows Task Manager. — GUI替代方案推荐 - -## Key Concepts -- [[TUI]]：文本用户界面，在终端运行的交互式图形化程序 -- [[Resource Monitor]]：系统资源监控工具，用于追踪CPU/内存/磁盘/网络使用情况 -- [[Process Management]]：进程管理，包括查看、搜索、终止、优先级调整 -- [[System Monitoring]]：系统监控，覆盖硬件资源与运行状态的实时观测 -- [[SSH Remote Access]]：通过SSH远程访问服务器进行系统管理 - -## Key Entities -- [[Btop++]]：作者的Top Pick TUI资源监控器，支持主题定制和信号发送 -- [[Htop]]：轻量级TUI进程监控器，键盘驱动（F3/F7/F8/F9） -- [[Glances]]：超轻量键盘驱动监控器，支持Arch/Debian/Snap安装 -- [[Bottom]]：专注实时图表的TUI监控器，支持进程树视图 -- [[Mission Center]]：类Windows任务管理器的GUI监控应用，支持Snap安装 -- [[Stacer]]：功能最全的GUI监控工具，包含系统维护套件 -- [[HowToGeek]]：技术博客，文章来源 - -## Connections -- [[TUI]] ← 应用类型 ← [[Btop++]], [[Htop]], [[Glances]], [[Bottom]] -- [[GUI]] ← 应用类型 ← [[Mission Center]], [[Stacer]] -- [[Process Management]] ← 核心功能 ← [[Btop++]], [[Htop]], [[Glances]], [[Mission Center]], [[Stacer]] -- [[System Monitoring]] ← 核心功能 ← all 6 tools -- [[SSH Remote Access]] ← 使用场景增强 ← [[TUI]] tools - -## Contradictions -- 无已知冲突 - -## Metadata -- **Author**: shenwei -- **Published**: 2025-12-16 -- **Source URL**: https://www.howtogeek.com/these-linux-apps-let-you-monitor-system-resources-in-style/ -- **Platform**: Linux -- **License**: HowToGeek +--- +title: "These 6 Linux Apps Let You Monitor System Resources in Style" +type: source +tags: [linux, system-monitoring, open-source, devops, tooling] +date: 2025-12-16 +--- + +## Source File +- [[Cloud & DevOps/These 6 Linux apps let you monitor system resources in style.md]] + +## Summary（用中文描述） +- 核心主题：Linux 系统资源监控工具横向评测，推荐 6 款替代桌面环境默认资源管理器的应用 +- 问题域：Linux 用户需要比桌面默认资源管理器更轻量、更美观或功能更丰富的系统监控方案 +- 方法/机制：按 TUI（命令行文本界面）和 GUI 两大类，分别评测 6 款工具的功能与体验 +- 结论/价值：作者首推 **Btop++**（TUI 类），理由是兼具美观与可用性；GUI 类首选 **Mission Center**（类 Task Manager 体验）和 **Stacer**（功能最丰富）；TUI 工具在 SSH 远程场景下尤为实用 + +## Key Claims（用中文描述） +- Btop++：主体（TUI 监控工具）+ 机制（多面板布局、支持进程信号/Nice 值/主题切换）+ 结果（作者首选） +- Htop：主体（TUI 进程监控）+ 机制（键盘驱动/F 键操作）+ 结果（适合追求极简流程监控的用户） +- Glances：主体（轻量 TUI 监控）+ 机制（全键盘导航/k 键杀进程）+ 结果（最轻最快） +- Bottom：主体（实时图形化资源监控）+ 机制（专注 CPU/网络/内存图表，非任务管理器）+ 结果（纯图形监控，无交互） +- Mission Center：主体（GNOME 原生 GUI 资源管理器）+ 机制（性能/应用/服务三标签页，类 Task Manager）+ 结果（Debian/Ubuntu 仅有 Snap 包） +- Stacer：主体（功能最全面的 GUI 资源管理器）+ 机制（仪表盘/进程/服务/启动项/APT 仓库/缓存清理）+ 结果（唯一支持桌面定制和垃圾清理的工具） + +## Key Quotes +> "TUI apps make the best resource monitors, in my opinion. They're snappy and responsive, even when the GUI is lagging." — 作者偏好 TUI 的核心理由 +> "Btop++ always gets my vote. It features a nice balance between usability and aesthetics." — Btop++ 推荐结论 +> "Mission Center is your friend" if you want something close to the Windows Task Manager — Mission Center 推荐定位 + +## Key Concepts +- [[TUI]]：文本用户界面，通过终端运行，响应迅速，适合 SSH 远程场景 +- [[System-Monitoring]]：系统资源监控，涵盖 CPU、内存、存储、网络、进程等维度 +- [[Process-Management]]：进程管理，包括查看、搜索、终止、优先级调整 + +## Key Entities +- [[Btop++]]：作者首选 TUI 资源监控器，支持 Pacman 安装和 Snap 包（Debian/Ubuntu） +- [[Htop]]：经典 TUI 进程监控器，全键盘驱动，适合进程优先场景 +- [[Glances]]：极轻量 TUI 监控器，全键盘操作，适合资源受限环境 +- [[Bottom]]：专注实时图形化监控的工具，支持进程树视图，非交互式任务管理器 +- [[Mission-Center]]：GNOME 原生 GUI 资源管理器，提供性能/应用/服务三标签页 +- [[Stacer]]：功能最丰富的 GUI 资源管理器，支持缓存清理、启动项管理、APT 仓库配置 +- [[HowToGeek]]：文章来源的技术博客 + +## Connections +- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]] ← 应用层 ← [[These-6-Linux-Apps-Let-You-Monitor-System-Resources-in-Style]]：本文工具为单机能见度层，与 Prometheus/Grafana 企业监控方案互补 +- [[linux-运维必会的-150-个命令]] ← 关联 ← [[These-6-Linux-Apps-Let-You-Monitor-System-Resources-in-Style]]：系统监控是 Linux 运维基础技能，本文 6 款工具覆盖该技能核心场景 +- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]] ← 对比 ← [[These-6-Linux-Apps-Let-You-Monitor-System-Resources-in-Style]]：企业级（Prometheus/Grafana）vs 轻量级（本文工具） + +## Contradictions +- 与 [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]] 定位差异： + - 冲突点：监控方案选择 + - 当前观点：单机能见度优先，用 Btop++ 或 Mission Center 快速定位问题 + - 对方观点：企业级基础设施需 Prometheus + Grafana 实现集中可观测性 + - 说明：两者面向不同场景，不构成直接冲突；建议单节点用本文工具，多节点/生产环境用 Prometheus/Grafana diff --git a/wiki/sources/what-i-know-about-cloud-service-delivery-1.md b/wiki/sources/what-i-know-about-cloud-service-delivery-1.md index 6aba3dc8..262c249d 100644 --- a/wiki/sources/what-i-know-about-cloud-service-delivery-1.md +++ b/wiki/sources/what-i-know-about-cloud-service-delivery-1.md @@ -1,92 +1,66 @@ ---- -title: "What I Know About Cloud Service Delivery 1" -source: -author: shenwei -published: -created: -description: -tags: [] -link: ---- - -## Source File -- [[raw/Cloud & DevOps/What I know about Cloud Service Delivery 1.md]] - -## Summary - -This document provides a comprehensive overview of **Cloud Service Delivery**, defining it as the bridge between raw cloud technology capabilities (IaaS, PaaS, SaaS) and the reliable, secure, performant, and cost-effective services that businesses and users consume. It covers the organizational structure of a Cloud Service Delivery team, 12 functional domains of cloud service delivery operations, and introduces the Cloud DevOps Maturity Model and AIOps concepts. - -## Key Concepts - -### Core Concepts -- [[Cloud Service Delivery]] — The entire lifecycle of making cloud services operational, available, secure, performant, and valuable to end-users -- [[Cloud Service Delivery Team]] — Multi-disciplinary team: Cloud Infrastructure Engineer, Cloud Operation Engineer (DevOps/SRE), Cloud Security Specialists, Cloud Support Engineer, Cloud FinOps Engineer -- [[Cloud DevOps Maturity Model]] — Maturity framework for evaluating cloud DevOps capabilities -- [[AIOps]] — Artificial Intelligence for IT Operations - -### Operational Domains -1. [[Service Provisioning & Deployment]] — Setting up cloud infrastructure, automating deployments, configuring services, managing resource allocation and scaling -2. [[Infrastructure Management]] — Monitoring health/performance/capacity, patching, managing physical data center aspects, ensuring HA and DR -3. [[Platform Management (PaaS)]] — Managing middleware, databases, development tools, runtime environments, platform scalability/security/performance -4. [[Application Operations & Management]] — Monitoring app performance, deploying updates, managing configuration and secrets, ensuring scalability and resilience -5. [[Security & Compliance Management]] — Implementing security controls (firewalls, IDS/IPS, encryption, IAM), vulnerability scanning, incident response, regulatory compliance (GDPR, HIPAA, PCI-DSS), auditing -6. [[Performance & Availability Monitoring]] — 24/7 monitoring, SLA/SLO tracking, proactive detection, incident response -7. [[Incident & Problem Management]] — Responding to alerts, troubleshooting, incident management, problem management (root cause analysis) -8. [[Change & Configuration Management]] — Change control, Infrastructure as Code (IaC), testing and rollback plans -9. [[Cost Management & Optimization]] — Monitoring consumption, eliminating waste, right-sizing, reserved instances/savings plans -10. [[Customer Onboarding & Support]] — User setup, documentation, helpdesk/service desk, billing inquiries -11. [[Service Governance & Lifecycle Management]] — Service catalogs, SLAs, service lifecycle (introduction, operation, retirement), continuous improvement, vendor management -12. [[Backup, Recovery & Disaster Management]] — Backup strategies, restore testing, DR plans, failover/failback procedures - -### Related Concepts -- [[SLA]] — Service Level Agreement (e.g., 99.9% vs 99.99% uptime) -- [[SLO]] — Service Level Objective -- [[IaC]] — Infrastructure as Code -- [[FinOps]] — Cloud financial management -- [[DevOps]] — Development and Operations integration -- [[SRE]] — Site Reliability Engineering -- [[WAF]] — Web Application Firewall -- [[APM]] — Application Performance Monitoring -- [[BPM]] — Business Performance Monitoring - -## Best Practices Mentioned - -| Domain | Best Practice | -|--------|---------------| -| Infrastructure Monitoring | AWS CloudWatch as data source in Grafana | -| Security | Cloud Application WAF management, IP whitelist to tenant level, Security Scanning | -| Availability | Service Availability Check (APM/BPM, New Relic, AWS CloudWatch Synthetic, Health Page) | -| Uptime | SLA 99.9% vs 99.99% ([uptime.is](https://uptime.is/)) | -| Alerting | Grafana Alerting with different severity levels | -| Change Management | Planned Change vs Emergency Change | - -## Key Insights - -1. **Cloud Service Delivery is a Bridge**: It connects raw IaaS/PaaS/SaaS capabilities to the reliable, secure, performant services that end users actually consume. - -2. **Multi-Disciplinary Team Required**: Effective cloud service delivery requires diverse roles — infrastructure engineers, DevOps/SRE, security specialists, support engineers, and FinOps. - -3. **12 Functional Domains**: From provisioning to disaster recovery, cloud service delivery spans the entire service lifecycle. - -4. **Monitoring is Foundational**: 24/7 monitoring with SLA/SLO tracking and proactive alerting (Grafana) is essential. - -5. **Security is Layered**: WAF, IP whitelisting, security scanning, and compliance (GDPR, HIPAA, PCI-DSS) must be integrated throughout. - -6. **Cost Awareness**: FinOps practices — eliminating waste, right-sizing, reserved instances — are critical for cloud ROI. - -7. **Maturity Model**: Organizations should assess their cloud DevOps maturity and progress systematically. - -## Connections to Other Sources - -- Related to [[Cloud Operating Model]] — strategies and best practices for cloud operations -- Related to [[Cloud Maturity Model]] — 5 maturity levels for cloud adoption -- Related to [[DevOps Maturity Model]] — from traditional IT to advanced DevOps -- Related to [[FinOps]] practices in cloud cost optimization -- Related to [[ITSM]] frameworks for service management - -## Metadata - -- **Author**: shenwei -- **Source File**: raw/Cloud & DevOps/What I know about Cloud Service Delivery 1.md -- **Created**: -- **Tags**: Cloud, DevOps, IT Operations, Cloud Infrastructure +--- +title: "What I Know About Cloud Service Delivery 1" +type: source +tags: [] +date: +author: shenwei +sources: [] +last_updated: 2026-04-26 +--- + +## Source File +- [[Cloud & DevOps/What I know about Cloud Service Delivery 1]] + +## Summary（用中文描述） +- **核心主题**：云服务交付（Cloud Service Delivery）的完整生命周期管理框架，涵盖从基础设施到客户支持的 12 大领域 +- **问题域**：如何将云技术（IaaS/PaaS/SaaS）的能力可靠、安全、高性能且成本有效地传递给最终用户 +- **方法/机制**：由多角色 Cloud Service Delivery Team 驱动，通过 IaC、监控、合规、成本优化等手段实现端到端管理 +- **结论/价值**：云服务交付是连接云技术能力与企业/用户实际需求之间的桥梁，需要多学科协作和持续运营 + +## Key Claims（用中文描述） +- Cloud Service Delivery Team（多角色团队）→ 通过专业分工 → 实现完整的云服务生命周期管理 +- Service Provisioning & Deployment → 自动化部署 + 资源配置和扩缩容 → 提高部署效率、加快交付速度 +- Infrastructure Management → 监控 + 补丁更新 + 高可用设置 → 确保底层基础设施稳定运行 +- Platform Management（PaaS）→ 中间件、数据库、开发工具和运行时管理 → 保证平台可扩展、安全、高性能 +- Application Operations & Management → 应用性能监控 + 持续部署 + 配置和密钥管理 → 确保应用弹性和可扩展性 +- Security & Compliance Management → 防火墙、IDS/IPS、加密、IAM 合规审计 → 保障云环境安全和合规 +- Performance & Availability Monitoring → 24/7 全栈监控 + SLA/SLO 管理 + 主动检测 → 确保服务高可用和性能达标 +- Incident & Problem Management → 快速响应 + 全栈故障排除 + 根因分析 → 最小化服务中断时间和影响 +- Change & Configuration Management → IaC + 变更控制 + 测试和回滚 → 降低变更风险、保证环境一致性 +- Cost Management & Optimization → 消费监控 + 消除浪费 + 合理选型（Savings Plans）→ 降低云支出、提升 ROI +- Customer Onboarding & Support → 用户引导 + 文档培训 + 服务台运营 → 提升用户体验和满意度 +- Backup, Recovery & Disaster Management → 备份策略 + 恢复测试 + DR 演练 → 确保业务连续性和数据安全 + +## Key Quotes + +## Key Concepts +- [[Cloud Service Delivery]]：将云技术（IaaS/PaaS/SaaS）能力可靠、安全、高性能且成本有效地传递给最终用户的完整生命周期管理 +- [[Infrastructure as Code (IaC)]]：通过代码管理基础设施配置，确保一致性和可重复性（Change & Configuration Management） +- [[Service Level Agreement (SLA)]]：服务等级协议，定义服务的可用性目标（如 99.9% vs 99.99%） +- [[Service Level Objective (SLO)]]：服务等级目标，SLA 分解到具体服务的具体指标 +- [[FinOps]]：云财务管理，通过监控消费、消除浪费、合理选型来优化云成本 +- [[Incident Management]]：事件管理，快速响应和恢复服务中断 +- [[Problem Management]]：问题管理，识别根因并实施永久性修复 +- [[Disaster Recovery (DR)]]：灾难恢复，确保业务连续性的备份和故障切换机制 +- [[Cloud DevOps Maturity Model]]：云 DevOps 成熟度模型（本文件末尾提及，待扩展） +- [[AIOps]]：人工智能运维（本文件末尾提及，待扩展） + +## Key Entities +- **AWS CloudWatch**：AWS 原生监控数据源，可接入 Grafana 实现统一可观测性 +- **Grafana**：监控可视化平台，支持 AWS CloudWatch 等多数据源 +- **New Relic**：APM/BPM 应用性能监控工具 +- **AWS CloudWatch Synthetic**：AWS 提供的服务可用性主动检测（Synthetic Monitoring）工具 +- **WAF (Web Application Firewall)**：云应用防火墙，管理云应用程序安全 +- **OpenText**：（作者所在组织）企业级云服务提供商 + +## Connections +- [[Cloud Maturity Model - A Detailed Guide For Cloud Adoption]] ← related_to ← [[What I Know About Cloud Service Delivery 1]] +- [[DevOps Culture and Transformation]] ← extends ← [[What I Know About Cloud Service Delivery 1]] +- [[Public Cloud Learning Sessions - Observability with OpenTelemetry]] ← related_to ← [[What I Know About Cloud Service Delivery 1]]（可观测性层面） +- [[CTP Topic 8 - Implementation of Cloud Monitoring]] ← related_to ← [[What I Know About Cloud Service Delivery 1]]（监控实践） +- [[Public Cloud Learning Sessions - Reducing Cloud Costs]] ← extends ← [[What I Know About Cloud Service Delivery 1]]（成本管理） +- [[Public Cloud Learning Sessions - EKS Optimization]] ← related_to ← [[What I Know About Cloud Service Delivery 1]]（平台管理） +- [[CTP Topic 73 AWS Backup Implementation]] ← related_to ← [[What I Know About Cloud Service Delivery 1]]（备份与灾难恢复） + +## Contradictions +- 与 [[DevOps Maturity Model From Traditional IT to Advanced DevOps]] 潜在交叉：两者均涉及 DevOps 文化成熟度，但本文更侧重运营层面，后者侧重文化转型；暂无实质性冲突 diff --git a/wiki/sources/what-is-devsecops-best-practices-benefits-and-tools.md b/wiki/sources/what-is-devsecops-best-practices-benefits-and-tools.md index a46d6edc..202860fa 100644 --- a/wiki/sources/what-is-devsecops-best-practices-benefits-and-tools.md +++ b/wiki/sources/what-is-devsecops-best-practices-benefits-and-tools.md @@ -1,112 +1,62 @@ ---- -title: "What is DevSecOps? Best Practices, Benefits, and Tools" -type: source -tags: [DevSecOps, Security, CI/CD, SDLC] -date: 2025-12-19 -source: https://www.bacancytechnology.com/blog/what-is-devsecops -author: shenwei -published: 2023-10-30 ---- - -## Source File -- [[raw/Cloud & DevOps/What is DevSecOps Best Practices, Benefits, and Tools.md]] - -## Summary (中文摘要) -- **核心主题**：DevSecOps 将安全实践深度集成到软件开发全生命周期的方法论，解决传统 DevOps 中安全滞后的问题 -- **问题域**：软件安全开发、安全自动化、DevOps 文化转型、企业安全合规 -- **方法/机制**：通过 Shift Left（安全左移）和 Shift Right（安全右移）策略，在 SDLC 各阶段嵌入安全检查；通过 SAST/DAST/IAST/SCA 等工具实现自动化安全测试 -- **结论/价值**：DevSecOps 可将 70% 的上线后漏洞在开发阶段预防，成本效益比传统安全实践高 3-5 倍 - -## Key Claims (中文描述) -- DevSecOps 通过在 CI/CD 流程中集成安全检查，使开发团队比传统团队能更好地处理安全问题 -- 70% 的上线后发现的安全漏洞本可以通过 DevSecOps 预防 -- 安全自动化将漏洞修复时间从数周缩短到数小时 -- DevSecOps 涵盖五大核心要素：协作（Collaboration）、沟通（Communication）、自动化（Automation）、工具与架构安全（Security of Tools and Architecture）、测试（Testing） -- Shift Left 策略通过早期发现安全问题，降低修复成本可达 100 倍 - -## Key Quotes -> "DevSecOps brings together three important groups: 'Dev' for development, 'Sec' for security, and 'Ops' for operations teams." — DevSecOps 命名来源 - -> "70% of software vulnerabilities discovered post-launch could have been prevented with DevSecOps" — DevSecOps 核心价值主张 - -> "'Shift left' means identifying security flaws early in the software development lifecycle." — 安全左移定义 - -> "'Shift right' highlights the need for ongoing security measures even after launching the application." — 安全右移定义 - -## Key Concepts -- [[DevSecOps]]：将安全深度集成到 DevOps 流程中的方法论，使安全成为开发、运维、安全团队的共同责任 -- [[Shift-Left-Security]]：安全测试左移到软件开发生命周期早期阶段的实践，降低修复成本 -- [[Shift-Right-Security]]：在生产环境部署后持续进行安全监控和响应的实践 -- [[SAST]]（Static Application Security Testing）：静态应用安全测试，分析源代码发现安全漏洞 -- [[DAST]]（Dynamic Application Security Testing）：动态应用安全测试，通过模拟外部攻击发现运行时刻漏洞 -- [[IAST]]（Interactive Application Security Testing）：交互式应用安全测试，在运行时检测漏洞 -- [[SCA]]（Software Composition Analysis）：软件组成分析，扫描第三方依赖中的已知漏洞 -- [[SDLC]]（Software Development Lifecycle）：软件开发生命周期，包括需求分析、规划、架构设计、开发、测试、部署六阶段 -- [[Break-the-Build]]：当安全风险过高时自动停止构建进程的机制 -- [[Policy-as-Code]]：以代码形式定义和管理安全策略的实践 -- [[Immutable-Infrastructure]]：不可变基础设施，通过预配置组件减少未授权变更风险 - -## Key Entities -- [[Amazon-Inspector]]：AWS 漏洞管理服务，可自动处理安全漏洞 -- [[Amazon-CodeGuru-Reviewer]]：AWS 代码审查服务，识别安全问题和资源泄漏 -- [[AWS-CodePipeline]]：AWS CI/CD 服务，用于应用部署和管理 -- [[Snyk]]：开源安全工具，集成到 DevSecOps 工具链 -- [[SonarQube]]：代码质量和安全静态分析工具 -- [[Jenkins]]：开源 CI/CD 工具（DevOps 工具） -- [[Docker]]：容器化平台（DevOps 工具） -- [[Kubernetes]]：容器编排平台（DevOps 工具） - -## DevSecOps vs DevOps Comparison - -| 维度 | DevOps | DevSecOps | -|------|--------|-----------| -| **定义** | 强调开发与运维协作加速交付 | 将安全实践集成到开发过程 | -| **主焦点** | 加速软件开发与部署 | 在每个开发阶段集成安全 | -| **安全角色** | 安全单独处理或最后处理 | 从一开始就将安全嵌入每个步骤 | -| **目标** | 提升团队速度和协作 | 早期解决安全问题预防后续问题 | -| **自动化** | 自动化开发与运维任务 | 自动化安全检查与开发任务 | -| **团队参与** | 开发与运维协作 | 开发、运维、安全三方协作 | -| **合规方式** | 开发后进行合规检查 | 开发部署全程确保合规 | - -## DevSecOps 核心组件 - -### 1. 协作（Collaboration） -- 安全任务在开发和运维团队间共享 -- 不需要独立的安全团队 -- 开发者被鼓励理解安全实践 - -### 2. 沟通（Communication） -- 安全专业人员需要用开发者理解的简单语言解释安全控制 -- 开发者应了解安全责任，识别潜在威胁，遵循安全编码最佳实践 -- 在开发过程中进行漏洞测试 - -### 3. 自动化（Automation） -- 将自动化安全测试添加到 CI/CD 管道 -- "Break the Build" 机制在安全风险过高时停止构建 -- 确保软件依赖保持最新 - -### 4. 工具与架构安全（Security of Tools and Architecture） -- 选择和审查安全工具 -- 谨慎管理用户访问（多因素认证、最小权限） -- 定期监控工作站和服务器漏洞 -- 扫描代码中的敏感数据 -- 新容器配置安全设置 - -### 5. 测试（Testing） -- 在每个开发阶段集成安全测试 -- 使用 OWASP Top Ten 进行基础安全测试 -- SAST/DAST/IAST 技术 -- 渗透测试和威胁建模 -- Bug Bounty 计划 - -## Connections -- [[DevOps]] ← extends ← [[DevSecOps]]（DevSecOps 是 DevOps 的安全扩展） -- [[Agile-Practices]] ← integrates_with ← [[DevSecOps]]（敏捷开发与 DevSecOps 相辅相成） -- [[CI/CD-Pipeline]] ← embeds ← [[DevSecOps-Security-Tools]]（安全工具集成到 CI/CD 管道） -- [[Cloud-Transformation]] ← includes ← [[DevSecOps]]（云转型包含 DevSecOps 实践） -- [[Shift-Left-Security]] ← complements ← [[Shift-Right-Security]]（左移与右移互补） - -## Contradictions -- **安全与速度的张力**：传统观点认为安全检查会减慢开发速度；DevSecOps 主张通过自动化实现安全与速度双赢 -- **集中式 vs 分布式安全**：传统安全团队独立负责安全；DevSecOps 倡导安全责任分散到整个开发团队 -- **合规时机**：传统做法在开发后进行合规检查；DevSecOps 强调全程合规 +--- +title: "What is DevSecOps? Best Practices, Benefits, and Tools" +type: source +tags: [] +date: 2023-10-30 +--- + +## Source File +- [[Cloud & DevOps/What is DevSecOps Best Practices, Benefits, and Tools]] + +## Summary（用中文描述） +- 核心主题：DevSecOps 将安全实践深度嵌入软件开发生命周期（SDLC），实现"安全即代码" +- 问题域：传统 DevOps 在后期才引入安全导致漏洞修复成本高、交付速度慢的问题 +- 方法/机制：通过 Shift Left（左移）和 Shift Right（右移）策略，在 CI/CD 流水线中集成 SAST/DAST/SCA/IAST 等自动化安全工具，培养"全员安全责任"文化 +- 结论/价值：DevSecOps 能将 70% 的上线后发现的安全漏洞提前预防，实现安全与速度的平衡 + +## Key Claims（用中文描述） +- 70% 的软件漏洞可在 DevSecOps 实践中被预防 +- 安全左移（Shift Left）使团队能在开发早期发现并修复安全问题，降低修复成本 +- 自动化安全测试集成到 CI/CD 流水线中，可在不减缓开发速度的前提下保障安全 +- DevSecOps 通过"break the build"机制，当安全风险过高时停止构建流程 +- SAST、DAST、SCA、IAST 四类安全工具分别覆盖代码编写、运行时、第三方依赖和交互测试等不同阶段 + +## Key Quotes +> "DevSecOps is a working methodology that includes security checks throughout the software development process." — DevSecOps 核心定义 + +> "70% of software vulnerabilities discovered post-launch could have been prevented with DevSecOps" — DevSecOps 价值量化 + +> "Everyone in the organization developing software is liable for security." — 全员安全责任文化 + +> "Shift left means identifying security flaws early in the software development lifecycle." — 左移策略定义 + +## Key Concepts +- [[DevSecOps]]：在 DevOps 中全程集成安全实践的工作方法论 +- [[Shift Left]]：在软件开发生命周期早期识别并修复安全缺陷的策略 +- [[Shift Right]]：在应用上线后持续进行安全监控和问题修复的策略 +- [[SAST]]：静态应用安全测试，在代码编写阶段分析源代码以发现漏洞 +- [[DAST]]：动态应用安全测试，模拟外部攻击从运行时发现漏洞 +- [[SCA]]：软件成分分析，扫描第三方依赖库和框架的已知安全漏洞 +- [[IAST]]：交互式应用安全测试，在应用运行时检测其他工具遗漏的漏洞 +- [[CI/CD 安全]]：在持续集成/持续交付流水线中自动化执行安全扫描 +- [[Break the Build]]：当安全风险超过阈值时自动停止构建流程的机制 +- [[Policy as Code]]：以代码形式定义和自动执行安全策略的方法 + +## Key Entities +- [[OWASP Top Ten]]：Web 应用安全标准，DevSecOps 测试中的重要参考框架 +- [[AWS CodePipeline]]：AWS 的 CI/CD 工具，可集成安全扫描 +- [[Amazon Inspector]]：AWS 漏洞管理自动化工具 +- [[Amazon CodeGuru Reviewer]]：AWS 代码安全和最佳实践审查工具 + +## Connections +- [[DevOps]] ← extends ← [[DevSecOps]]（DevSecOps 是 DevOps 的安全扩展） +- [[CI/CD 安全]] ← depends_on ← [[SAST]] / [[DAST]] / [[SCA]] / [[IAST]] +- [[DevSecOps]] ← applies ← [[Shift Left]] +- [[DevSecOps]] ← applies ← [[Shift Right]] +- [[Agile Development]] ← integrates ← [[DevSecOps]] + +## Contradictions +- 与传统瀑布式开发相比： + - 冲突点：传统方式在 SDLC 末期才进行安全测试 + - 当前观点：DevSecOps 强调安全全程嵌入 + - 对方观点：安全专家在开发完成后再统一介入更专业