Auto-sync: 2026-04-24 04:02
This commit is contained in:
@@ -1,44 +1,34 @@
|
||||
---
|
||||
title: AWS (Amazon Web Services)
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
title: "Amazon Web Services (AWS)"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Cloud
|
||||
- Hybrid-Cloud
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
# AWS (Amazon Web Services)
|
||||
## Amazon Web Services (AWS)
|
||||
|
||||
**AWS** is Amazon's cloud computing platform, providing a broad set of infrastructure and application services across 200+ fully featured services.
|
||||
Amazon Web Services (AWS) is the world's most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally.
|
||||
|
||||
## Overview
|
||||
## Aliases
|
||||
- AWS
|
||||
- Amazon Web Services
|
||||
|
||||
AWS is one of the three major public cloud providers (alongside Azure and Google Cloud), offering the most extensive range of services.
|
||||
## Key Partnerships
|
||||
- **VMware Cloud on AWS (VMC on AWS)**: AWS partnered with VMware to run VMware workloads natively on AWS infrastructure. The underlying hardware consists of i3.metal and i3en.metal bare metal servers, organized into clusters within availability zones and regions.
|
||||
|
||||
## Key Services Referenced
|
||||
## Infrastructure for VMC on AWS
|
||||
- **i3.metal**: Bare metal server instance used for VMware Cloud on AWS SDDC deployment
|
||||
- **i3en.metal**: Enhanced bare metal instance with larger storage capacity
|
||||
- **Clusters**: Organized within availability zones and regions globally
|
||||
- **Stretched Clusters**: Available across availability zones for increased resilience
|
||||
|
||||
| Category | Services |
|
||||
|---------|----------|
|
||||
| Compute | EC2, Lambda |
|
||||
| Storage | S3, EBS |
|
||||
| Database | RDS, DynamoDB, Aurora |
|
||||
| AI/ML | SageMaker, Bedrock |
|
||||
| Analytics | Redshift, Athena |
|
||||
| Networking | VPC, Route 53, CloudFront |
|
||||
| IaC & Deployment | CloudFormation, **CloudFormation StackSets** |
|
||||
| Observability | **EventBridge**, **CloudWatch Logs**, CloudWatch Logs Insights, CloudWatch Alarms |
|
||||
| Security & Identity | **KMS**, IAM, CloudTrail, Security Hub |
|
||||
| Organization | **AWS Organizations** |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
AWS is commonly used alongside Azure and Google Cloud in multi-cloud strategies:
|
||||
- **General infrastructure** — Often primary compute and storage provider
|
||||
- **Enterprise integration** — Strong Active Directory and enterprise app ecosystem
|
||||
- **Market position** — Largest market share among cloud providers
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — AWS as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on AWS-native services
|
||||
- [[FinOps]] — Managing AWS costs
|
||||
## Connections
|
||||
- [[VMware-Cloud-on-AWS]] ← powered_by ← [[AWS]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← source ← [[AWS]]
|
||||
- [[VMware]] ← partners ← [[AWS]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
|
||||
26
wiki/entities/Brendan-Starnig.md
Normal file
26
wiki/entities/Brendan-Starnig.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: "Brendan Starnig"
|
||||
type: entity
|
||||
tags: [SRE, Platform-Engineering, Change-Management]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Brendan Starnig is the SRE Function Lead in the Platform Engineering team. He is the primary presenter of CTP Topic 30 on Managing Change, which covers change management processes and SRE team collaboration patterns in cloud transformation projects.
|
||||
|
||||
## Role
|
||||
|
||||
- **Title**: SRE Function Lead, Platform Engineering
|
||||
- **Team**: Site Reliability Engineering (SRE)
|
||||
- **Topics**: Change Management, SRE Practices, Cloud Transformation
|
||||
|
||||
## Key Contributions
|
||||
|
||||
- Developed and presented the change management framework covering Standard Change, Normal Change, and Emergency Change
|
||||
- Defined SRE team collaboration model across three phases: Build / Early Live Support / BAU
|
||||
- Proposed Self-Healing automation initiative with product teams
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-30-managing-change]]
|
||||
22
wiki/entities/Heather-Norris.md
Normal file
22
wiki/entities/Heather-Norris.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: "Heather Norris"
|
||||
type: entity
|
||||
tags: []
|
||||
sources: []
|
||||
last_updated: 2026-04-24
|
||||
---
|
||||
|
||||
## 基本信息
|
||||
- **角色：** 云转型计划（Cloud Transformation Programme）项目经理
|
||||
- **演讲主题：** 在云转型项目中应用敏捷方法论（CTP Topic 4）
|
||||
|
||||
## 主要观点
|
||||
- 倡导 Scrum 向 Kanban 的框架演进，以适应云转型项目的高变化频率
|
||||
- 强调敏捷的核心价值是快速反馈循环，持续改进产品和开发文化
|
||||
- 推动 Microsoft Planner 作为团队统一的看板工具
|
||||
|
||||
## 参与项目
|
||||
- Cloud Transformation Programme (CTP)
|
||||
|
||||
## 来源
|
||||
- [[ctp-topic-4-using-agile-to-run-the-cloud-transformation-program]]
|
||||
31
wiki/entities/Microsoft-Planner.md
Normal file
31
wiki/entities/Microsoft-Planner.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: "Microsoft Planner"
|
||||
type: entity
|
||||
tags: []
|
||||
sources: []
|
||||
last_updated: 2026-04-24
|
||||
---
|
||||
|
||||
## 基本信息
|
||||
- **类型：** 项目管理工具 / 看板平台
|
||||
- **厂商：** Microsoft
|
||||
- **产品定位：** Microsoft 365 套件中的轻量级任务和项目可视化工具
|
||||
|
||||
## 主要用途
|
||||
- 云转型计划（CTP）团队的统一任务管理平台
|
||||
- 支持 Kanban 结构的看板管理
|
||||
|
||||
## 看板结构（CTP 场景）
|
||||
- **列：** Backlog → To Do → In Progress → Program Key Decisions → Icebox
|
||||
- **最佳实践：**
|
||||
- 每张任务卡必须指定单一负责人，即使多人协作
|
||||
- 明确角色定义（如 oversight）
|
||||
- 链接依赖关系卡
|
||||
- 设置优先级和截止日期
|
||||
- 优先级、日期、负责人、进度变更须通过卡片评论沟通
|
||||
|
||||
## 来源
|
||||
- [[ctp-topic-4-using-agile-to-run-the-cloud-transformation-program]]
|
||||
|
||||
## 别名
|
||||
- Microsoft Planner Board
|
||||
42
wiki/entities/SMACs.md
Normal file
42
wiki/entities/SMACs.md
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: "SMACs"
|
||||
type: entity
|
||||
tags: [ITSM, Service-Management, Change-Management, Incident-Management]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
SMACs (Service Management Automation X) is the current ITSM (IT Service Management) tool used within the organization for managing Tickets, Incidents, Changes, and related service workflows. It replaces the legacy semantic messaging gateway for email and serves as the unified platform for IT service operations.
|
||||
|
||||
## Full Name
|
||||
|
||||
Service Management Automation X (formerly Micro Focus Operations Manager i / SMACKS)
|
||||
|
||||
## Key Functions
|
||||
|
||||
|| Function | Description |
|
||||
|---------|-------------|
|
||||
| Ticket Management | Create, track, and resolve IT service requests |
|
||||
| Incident Management | Handle low-level events that trigger alerts vs. major incidents |
|
||||
| Change Management | Manage Standard/Normal/Emergency change workflows |
|
||||
| Problem Management | Track root causes and CAPA/Post-mortem actions |
|
||||
|
||||
## Relationship with Change Management
|
||||
|
||||
In the change management framework (CTP Topic 30), SMACs is used to:
|
||||
- Log and track Change Records (CR)
|
||||
- Route Normal Changes to CAB for approval
|
||||
- Execute Emergency Changes with post-incident documentation
|
||||
- Link Changes to related Incidents for audit trail
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Standard-Change]]：预批准变更，在 SMACs 中可实现完全自动化审批
|
||||
- [[Normal-Change]]：需 CAB 审批，在 SMACs 中通过变更窗口管理
|
||||
- [[Emergency-Change]]：立即执行，在 SMACs 中事后通过 CAPA 补齐文档
|
||||
- [[CAPA]]：Corrective and Preventive Action，在 SMACs 中作为 Post-mortem 流程落地
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-30-managing-change]]
|
||||
@@ -13,10 +13,11 @@ SRE Team（Site Reliability Engineering 团队）是该组织中负责 AWS Landi
|
||||
|
||||
| 职责 | 说明 |
|
||||
|------|------|
|
||||
| 运维自动化 | 开发自动化工具减少人工重复操作 |
|
||||
| 运维自动化 | 开发自动化工具减少人工重复操作，通过 IaC + CI/CD 实现 Standard Change |
|
||||
| 工具开发 | 构建内部平台工具（如 Tag Validation Tool） |
|
||||
| 可靠性保障 | 确保 AWS 基础设施的高可用性和可观测性 |
|
||||
| 可靠性保障 | 确保 AWS 基础设施的高可用性和可观测性，定义 SLO/SLR 体系 |
|
||||
| 内部平台 | 维护 SRE Tools Repository 内部代码仓库 |
|
||||
| SRE 三阶段支持 | Build（构建）/Early Live Support（早期上线支持）/BAU（日常运维）三个阶段与产品团队协作 |
|
||||
|
||||
## SRE Tools Repository
|
||||
|
||||
@@ -37,3 +38,4 @@ SRE 团队维护的内部代码仓库（[[SRE-Tools-Repository]]），集中存
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-28-aws-tag-validation-tool]]
|
||||
- [[ctp-topic-30-managing-change]]
|
||||
|
||||
28
wiki/entities/SankarGopov.md
Normal file
28
wiki/entities/SankarGopov.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: "Sankar Gopov"
|
||||
type: entity
|
||||
tags: []
|
||||
sources: []
|
||||
last_updated: 2026-04-24
|
||||
---
|
||||
|
||||
## Sankar Gopov
|
||||
|
||||
AWS 网络与混合云架构专家，Cloud Transformation Programme (CTP) 的核心讲师之一。
|
||||
|
||||
## Role
|
||||
|
||||
- **CTP Topic 19**：AWS Landing Zone DNS 配置专题讲师
|
||||
- **CTP Topic 22**：Global DNS Service Offerings 讲师（与 Vino 联合主讲）
|
||||
|
||||
## Areas of Expertise
|
||||
|
||||
- AWS Landing Zone 多账号架构设计
|
||||
- Route 53 混合 DNS 架构（Inbound/Outbound Endpoints）
|
||||
- 企业级 DNS 服务架构（Infoblox + Route 53）
|
||||
- 跨账号 VPC 网络互联
|
||||
|
||||
## Connections
|
||||
|
||||
- 通过 [[ctp-topic-19-configuring-dns-within-aws-lzs]] 讲解 Landing Zone 内部 DNS 配置
|
||||
- 通过 [[ctp-topic-22-global-dns-service-offerings]] 讲解企业级全局 DNS 架构
|
||||
40
wiki/entities/VMware.md
Normal file
40
wiki/entities/VMware.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: "VMware"
|
||||
type: entity
|
||||
tags:
|
||||
- VMware
|
||||
- Virtualization
|
||||
- Hybrid-Cloud
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## VMware
|
||||
|
||||
Enterprise virtualization and cloud computing software provider. Headquartered in Palo Alto, California, VMware is known for its vSphere hypervisor and vCenter management platform.
|
||||
|
||||
## Aliases
|
||||
- VMware, Inc.
|
||||
- VMware Cloud
|
||||
|
||||
## Overview
|
||||
VMware partnered with AWS to develop **VMware Cloud on AWS (VMC on AWS)**, a jointly engineered cloud service where the VMware hypervisor runs natively on AWS bare metal servers (i3.metal / i3en.metal). This is not a simple deployment of VMware software onto cloud infrastructure — it is a true joint engineering effort between VMware and AWS.
|
||||
|
||||
## Key Offerings
|
||||
- **vSphere**: Enterprise virtualization platform
|
||||
- **vCenter**: Centralized management for vSphere environments
|
||||
- **HCX (Hybrid Cloud Extension)**: Enables any-to-any vSphere workload migration between on-premises and cloud
|
||||
- **VMC on AWS**: VMware Cloud on AWS jointly engineered with Amazon Web Services
|
||||
|
||||
## Key People
|
||||
- Brian Reeves — VMware speaker, discussed VMC on AWS economics (27% cost savings vs. regular cloud)
|
||||
- Michael Riley — VMware speaker
|
||||
- Mike Armstrong — VMware speaker
|
||||
- Mike O'Reilly — Staff Cloud Solutions Architect at VMware, explained VMC on AWS technical architecture
|
||||
|
||||
## Connections
|
||||
- [[VMware-Cloud-on-AWS]] ← provides ← [[AWS]] infrastructure partnership
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← source ← [[VMware]]
|
||||
- [[ctp-topic-69-best-practices-for-migrating-on-premises-iod-virtual-machines-to-vm]] ← related_to ← [[VMware]]
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
Reference in New Issue
Block a user