Sync: add infrastructure as code notes
This commit is contained in:
84
wiki/log.md
84
wiki/log.md
@@ -1,3 +1,70 @@
|
||||
## [2026-05-05] ingest | CTP Topic 16 Cross-account Terraform modules
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/03_Terraform/ctp-topic-16-cross-account-terraform-modules.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Fibos 主讲,多账号 AWS 环境中跨账号 Terraform 模块的中心化部署方案——基于 Shared Account(共享账号)作为中转站,Jenkins + ECS Deploy Runner + Assume Role 三联动。核心机制:Jenkins 检测 `cross-account.json` 标记文件触发 ECS Deploy Runner,通过 Assume Role 访问目标账号的 TF state bucket accessor 和 cross-account ECS deploy runner role。三大目标:安全性(无 Workload 账号间直接信任)、自动化(Jenkins 自动识别模块类型)、可复用性(模块代码不硬编码特定账号角色)。
|
||||
- Concepts created: [[Cross-account-Terraform-Modules]]
|
||||
- Entities created: none(Gruntwork 已存在)
|
||||
- Source page: wiki/sources/ctp-topic-16-cross-account-terraform-modules.md
|
||||
- Notes: index.md 已替换占位符条目;overview.md 已新增独立段落(置于 ECS Deployment 和 Topic 21 之间);Entity Jenkins/Fibos 提及次数不足建页阈值,以 wikilink 形式记录于 Source page;无实质性内容冲突,演进关系记录于 Contradictions 节
|
||||
|
||||
## [2026-05-05] ingest | Learning Sessions ECS Deployment using IAC - 20230808
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/03_Terraform/learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: JP 和 Raja M 主讲,CTP/SRE 团队通过 Terraform IaC 实现 ECS 容器化应用自动化部署——基于 Gruntwork 仓库构建 ECS 模块,支持 Docker 容器/EC2 部署;核心功能:自动扩缩容、自动故障恢复、金丝雀部署;Listener 集中管理方式;前置条件:VPC/ELB 安全组/EFS 卷挂载;集成 CloudWatch/Splunk/Grafana/Prometheus。ECS 作为 AWS 原生技术与 AWS 服务深度集成。
|
||||
- Concepts created: [[Canary-Deployment]], [[Infrastructure-as-Code]]
|
||||
- Entities created: [[Gruntwork]]
|
||||
- Source page: wiki/sources/learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording.md
|
||||
- Notes: index.md 已替换占位符条目;overview.md 已新增独立段落(置于 Terraform 工具选型后);ECS 与 EKS 选型冲突记录于 Contradictions 节;JP 和 Raja M 各出现 1 次,不足独立 Entity 建页阈值,以 wikilink 形式记录于 Source page;无其他内容冲突
|
||||
- Conflicts: 与 [[ctp-topic-64-scaling-out-with-amazon-eks]] 在容器编排选型上的差异——ECS 强调 AWS 原生集成,EKS 强调可移植性,两者适用于不同场景但可互补
|
||||
|
||||
## [2026-05-05] ingest | CTP Topic 48 Terraform vs Terragrunt
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/03_Terraform/ctp-topic-48-terraform-vs-terragrunt.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Bob(AWS Solutions Architect)对比 Terraform 与 Terragrunt——Terraform(HashiCorp 出品)是云厂商无关的 Golang 应用,通过状态文件绑定期望状态与实际环境;Terragrunt 是轻量封装,贯彻 DRY 原则,管理 provider 和 remote_state 块减少跨环境重复声明。两者命令和语法高度一致,Terragrunt 通过减少硬编码优化大规模企业部署。辅助工具:Terraform Enterprise、Gruntwork、Atlantis、tfsec、Terratest
|
||||
- Concepts created: [[DRY Principle]], [[State-File-Management]]
|
||||
- Entities created: [[HashiCorp]], [[Terragrunt]], [[Atlantis]]
|
||||
- Entities updated: [[Terraform]], [[Gruntwork]]
|
||||
- Concepts updated: [[Infrastructure-as-Code]]
|
||||
- Source page: wiki/sources/ctp-topic-48-terraform-vs-terragrunt.md
|
||||
- Notes: 视频由 Gemini 摘要,原文状态为 "summarized (Gemini 摘要)";来源 NAS 路径为 `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 48_ Terraform vs Terragrunt.mp4`
|
||||
|
||||
## [2026-05-05] ingest | Public Cloud Learning Sessions (OpenText) - AI Use Cases - 20241126 160106
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/09_Serverless_AI/public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: AWS AI 专家 Stephen Frank 分享 Gen2 AI 发展驱动力(数据爆发+算力提升)、企业级 AI 应用场景(客户体验/洞察提取/流程自动化/内容生成)、AWS 三层产品战略(基础设施→Bedrock→AI 应用)、数据差异化策略(RAG/Fine-tuning/持续预训练)、Amazon Q 企业知识问答、负责任 AI 原则
|
||||
- Concepts linked: [[RAG]], [[Fine-Tuning]], [[Continued-Pre-Training]], [[Responsible-AI]]
|
||||
- Entities linked: [[AWS]], [[Amazon-Bedrock]], [[Amazon-SageMaker]], [[Amazon-Q]], [[Stephen-Frank]]
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec.md
|
||||
- Notes: index.md 已替换占位符条目(日期修正为 2026-04-14);overview.md 已新增独立段落(Serverless & AI 专题,置于提示工程后);RAG/Fine-Tuning/Responsible-AI/Stephen-Frank/Amazon-Q/Amazon-SageMaker 在 wiki 中出现频次不足独立建页阈值,以 wikilink 形式记录于 Source page;无内容冲突
|
||||
- Conflicts: 无
|
||||
|
||||
## [2026-05-05] ingest | Public Cloud Learning Sessions (OpenText) - Event Driven Architecture Part 2 - 20240917
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/09_Serverless_AI/public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: EDA 进阶实践——三组件(事件生产者/消费者/代理)、事件路由器(EventBridge/SNS)与事件存储(SQS/Kinesis)、编排与编排模式(Choreography vs Orchestration)、幂等性、事件排序、去中心化团队所有权、Fan-out 模式、竞争消费者模式、死信队列、EventBridge 最佳实践
|
||||
- Concepts updated: [[Event-Driven-Architecture]](补充 Part 2 内容:EDA 三组件、编排模式对比、生产级最佳实践:幂等性/事件排序/团队独立性、扩展 Event Patterns:Fan-Out/Competing Consumer/DLQ)
|
||||
- Entities existing (no new): [[AWS]], [[Amazon-EventBridge]], [[Amazon-SQS]], [[Amazon-SNS]], [[AWS-Lambda]], [[AWS-Step-Functions]]
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091.md
|
||||
- Notes: index.md 已替换占位符条目(日期修正为 2026-05-05);overview.md 已添加 Part 2 独立段落(新增于 Serverless 段落和 Part 1 之间),同时更新 Part 1 引用指向 Part 2;Event-Driven-Architecture 概念页已更新 sources + last_updated,新增 EDA 三组件/编排模式/生产级最佳实践内容,扩展 Event Patterns;Kinesis-Data-Streams 出现 1 次,不足独立建 Entity 阈值,以 wikilink 形式记录于 Concept 页
|
||||
- Conflicts: 与 [[ctp-topic-64-scaling-out-with-amazon-eks]] 在扩展方式上的差异——EDA 通过事件驱动异步扩展(消费者按需处理),EKS 通过容器编排横向扩展(Pod 副本数调整),两者适用于不同场景但可互补使用
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/09_Serverless_AI/public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: EDA 入门——AWS 解决方案架构师 Dr. Anil Giri 介绍 EventBridge/SQS/SNS 事件驱动架构与 Enterprise Integration Patterns;会议因 Teams 屏幕共享故障仅完成开场介绍,完整演示参见 Part 2
|
||||
- Concepts linked: [[Event-Driven-Architecture]], [[Enterprise-Integration-Patterns]], [[Amazon-EventBridge]], [[Amazon-SQS]], [[Amazon-SNS]]
|
||||
- Entities linked: [[Dr.-Anil-Giri]], [[AWS]], [[OpenText]], [[Micro-Focus]]
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091.md
|
||||
- Notes: index.md 已替换占位符条目(日期修正为 2026-04-19);overview.md 已补充(Serverless & AI 专题段落新增,置于无服务器计算后);Dr. Anil Giri/AWS/OpenText/Micro Focus 在 wiki 中出现频次不足独立建 Entity 页阈值,以 wikilink 形式记录于 Source page;EventBridge/SQS/SNS/Enterprise-Integration-Patterns 概念频次不足独立建 Concept 页阈值;已建立与 Part 2(public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091)、无服务器计算(public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee)的 Connections 关系;冲突记录与 ctp-topic-64-scaling-out-with-amazon-eks 的扩展方式差异已记录于 Contradictions 节
|
||||
- Conflicts: 与 [[ctp-topic-64-scaling-out-with-amazon-eks]] 在扩展方式上的差异——EDA 通过事件驱动异步扩展,EKS 通过容器编排横向扩展,两者适用于不同场景但可互补使用
|
||||
|
||||
## [2026-05-05] ingest | Public Cloud Learning Sessions - Serverless Computing - 20240903
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: AWS 无服务器计算深度解析——Lambda 事件驱动模型(同步/异步/事件源映射)、Step Functions 状态机编排(Standard/Express)、API Gateway(边缘优化/区域/私有)、SAM 本地开发和部署;Serverless 业务价值(快速上市/按需付费/自动扩展/内置安全);AWS 与客户共担运维责任
|
||||
- Entities created: [[AWS-Lambda]], [[AWS-Step-Functions]], [[Amazon-API-Gateway]], [[SAM-Serverless-Application-Model]]
|
||||
- Concepts linked: [[Serverless-Computing]], [[Event-Driven-Architecture]]
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee.md
|
||||
- Notes: index.md 已更新(替换占位符条目,日期修正为 2026-04-14);overview.md 已补充(Cloud Transformation & DevOps 章节新增独立段落,置于 AI/ML 入门与 CTP Topic 20 之间);Entity 页均按字母顺序插入 index.md Entities 节;无内容冲突(Serverless-Computing 概念页已存在,内容一致)
|
||||
- Conflicts: 无
|
||||
|
||||
## [2026-05-05] ingest | Public Cloud Learning Sessions - Introduction to AI/ML with AWS
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/09_Serverless_AI/public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin.md
|
||||
- Status: ✅ 成功摄入
|
||||
@@ -2512,4 +2579,19 @@
|
||||
- overview.md 更新:新增条目于 Cloud Transformation & DevOps 章节 FinOps 知识链路
|
||||
- RightSizing/Cloud Cost Optimization 已通过 wikilink 嵌入 Source page
|
||||
- Key Entities: PCG (Platform Control Group) 已在 Wiki 中存在(ctp-topic-13),无需新建 Entity 页面
|
||||
- 冲突检测:未发现内容冲突,Contradictions 暂置空占位
|
||||
- 冲突检测:未发现内容冲突,Contradictions 暂置空占位
|
||||
|
||||
## [2026-05-06] ingest | Public Cloud Learning Sessions (OpenText) - Generative AI & Prompt Engineering - 20241112
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/09_Serverless_AI/public-cloud-learning-sessions-opentext-generative-ai-prompt-engineering-2024111.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: AWS 生成式 AI 服务与提示工程实践,由 OpenText 技术客户经理 Shikad Holtzman(以色列)主讲——生成式 AI 四大价值路径、企业数据差异化核心洞见、Amazon Bedrock 全托管基础模型服务(RAG/微调/Agents/Guardrails)、Amazon Q 助手(企业版/开发者版)、AWS 专用芯片(Trainium/Inferentia)、提示工程四组件(指令/上下文/用户输入/输出指示器)和基础技巧(One-shot/Few-shot、Chain of Thoughts)
|
||||
- Concepts linked: [[RAG]], [[Prompt-Engineering]], [[Chain-of-Thought]], [[One-Shot-Prompting]], [[Few-Shot-Prompting]], [[Responsible-AI]], [[Guardrails-for-Amazon-Bedrock]]
|
||||
- Entities linked: [[Shikad-Holtzman]], [[Amazon-Bedrock]], [[Amazon-SageMaker]], [[Amazon-Q]], [[AWS-Trainium]], [[AWS-Inferentia]], [[AWS]]
|
||||
- Source page: wiki/sources/public-cloud-learning-sessions-opentext-generative-ai-prompt-engineering-2024111.md
|
||||
- Notes:
|
||||
- index.md 已更新:将原 expected placeholder 更新为正式条目(2026-04-19),补充中文摘要
|
||||
- overview.md 已更新:在 Cloud Transformation & DevOps 章节的 AI/ML 入门条目后新增独立段落,与 AI/ML 入门共同构成生成式 AI 知识链路
|
||||
- Key Concepts:RAG/Prompt-Engineering/Chain-of-Thought/Few-Shot-Prompting 频次不足独立建 Concept 页阈值,以 wikilink 形式记录于 Source page
|
||||
- Key Entities:Shikad Holtzman 仅出现 1 次,以 wikilink 形式记录于 Source page;Amazon Bedrock/Q/SageMaker 在同系列其他来源中提及频次不足独立建 Entity 页阈值
|
||||
- 同系列来源关联:已建立与 AI/ML 入门(public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin)和无服务器计算(public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee)的 Connections 关系
|
||||
- 冲突检测:与 ctp-topic-64-scaling-out-with-amazon-eks 在扩展方式上的差异已记录于 Source page Contradictions(EDA 事件驱动 vs EKS 容器编排,适用于不同场景可互补)
|
||||
Reference in New Issue
Block a user