Auto-sync: 2026-04-29 00:02
This commit is contained in:
40
wiki/entities/AWS-Landing-Zone.md
Normal file
40
wiki/entities/AWS-Landing-Zone.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: "AWS Landing Zone"
|
||||
type: entity
|
||||
tags: ["AWS", "Landing-Zone", "Multi-Account", "Architecture"]
|
||||
sources: ["ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones", "ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security"]
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
AWS Landing Zone 是 AWS 推荐的多账户架构框架，用于建立安全、可扩展、合规的云基础架构基础。Micro Focus 采用基于 Gruntwork 的 Landing Zone 参考架构，通过 Terraform/Terragrunt 管理所有资源。
|
||||
|
||||
## Core Components
|
||||
- **Shared Services Account**：托管 Jenkins、AD、Route 53 私有 DNS 等共享基础设施
|
||||
- **Network Account**：Transit Gateway + Checkpoint 防火墙管理所有互联网流量
|
||||
- **Security Account**：联邦用户、跨账户访问、IAM Role 集中管理
|
||||
- **Logs Account**：CloudTrail、Config 日志集中存储
|
||||
- **Product/SaaS Accounts**：业务负载运行的账户
|
||||
|
||||
## Network Isolation Challenges
|
||||
在 [[ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones]] 中描述的安全挑战：
|
||||
- On-prem 系统和 VPN 用户因共享网络配置可直接访问生产工作负载
|
||||
- 解决路径：Checkpoint SPI（Default Deny）+ AWS SSM 替代 VPN
|
||||
|
||||
## Tag-Based Security Architecture
|
||||
在 [[ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security]] 中，Steve Jarman 和 Pradeep 深入阐述了基于标签的云原生安全架构：
|
||||
|
||||
- **SCP（Security Control Policy）强制标签规范**：通过「显式拒绝」逻辑防止用户通过篡改标签绕过审计，确保资源创建时即具备正确的 BU/产品/环境归属；普通 ADM 用户无法擅自将标签改为 ITOM
|
||||
- **OU 分层架构**：通过多层 OU 检查标签值，确保正确的标记和必要的安全控制
|
||||
- **标签体系**：涵盖机器名、所有者（PDL）、类型、业务单元、产品、环境、服务器角色等维度，是云迁移规划的前提
|
||||
- **Checkpoint 标签驱动策略**：从基于 IP 地址的传统防火墙规则转向利用 AWS 标签作为安全凭证，实现动态云环境
|
||||
|
||||
## Aliases
|
||||
- Landing Zone
|
||||
- LZ
|
||||
- AWS LZ
|
||||
|
||||
## Connections
|
||||
- [[Network-Segmentation]] — 网络隔离是 LZ 安全架构核心
|
||||
- [[AWS-SSM]] — SSM 提供 LZ 内安全远程访问
|
||||
- [[ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones]]
|
||||
@@ -5,8 +5,8 @@ tags:
|
||||
- AWS
|
||||
- Cloud
|
||||
- Hybrid-Cloud
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
last_updated: 2026-04-25
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices, public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2]
|
||||
last_updated: 2026-04-29
|
||||
---
|
||||
|
||||
## Amazon Web Services (AWS)
|
||||
@@ -30,7 +30,10 @@ Amazon Web Services (AWS) is the world's most comprehensive and broadly adopted
|
||||
- [[VMware-Cloud-on-AWS]] ← powered_by ← [[AWS]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← source ← [[AWS]]
|
||||
- [[VMware]] ← partners ← [[AWS]]
|
||||
- [[AWS-Transit-Gateway-TGW]] ← 服务 ← [[AWS]]
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] ← 平台 ← [[AWS]]
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
- [[ctp-topic-72-implementing-an-enterprise-dr-strategy-using-aws-backup.md]]
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]]
|
||||
|
||||
29
wiki/entities/BrianReeves.md
Normal file
29
wiki/entities/BrianReeves.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: "Brian Reeves"
|
||||
type: entity
|
||||
tags:
|
||||
- VMware
|
||||
- CTP
|
||||
- Cloud
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Brian Reeves
|
||||
|
||||
VMware speaker at Cloud Transformation Programme (CTP) learning sessions. Specializes in cloud economics and the business case for cloud migration.
|
||||
|
||||
## Role
|
||||
Speaker at CTP Topic 43 — VMware Cloud on AWS. Presented the economics perspective, highlighting that VMC on AWS offers 27% cost savings compared to regular cloud deployment.
|
||||
|
||||
## Key Points Covered
|
||||
- VMC on AWS cost model: VMware sells an entire host, enabling over-provisioning and cost reduction
|
||||
- TCO comparison: Cloud economics team can perform total cost of ownership calculations to compare VMC on AWS against on-premises or other hyperscalers
|
||||
- Business value: Positioned VMC on AWS as a middle ground for organizations not ready for full native cloud migration
|
||||
|
||||
## Connections
|
||||
- [[VMware]] ← speaker ← [[BrianReeves]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← presented_by ← [[BrianReeves]]
|
||||
- [[VMware-Cloud-on-AWS]] ← discusses ← [[BrianReeves]] economics perspective
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
48
wiki/entities/Checkpoint-Firewall.md
Normal file
48
wiki/entities/Checkpoint-Firewall.md
Normal file
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: "Checkpoint Firewall"
|
||||
type: entity
|
||||
tags: ["AWS", "Firewall", "Network-Security", "Checkpoint"]
|
||||
sources: ["ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones", "ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security"]
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
Checkpoint 是 Micro Focus AWS Landing Zone 网络架构中的核心防火墙设备，部署在 Network Account 中，负责管理所有互联网流量和跨区域网络隔离。
|
||||
|
||||
## Role in Landing Zone Architecture
|
||||
- 集中管理 Landing Zone 与 On-prem 之间的所有网络流量
|
||||
- 启用 SPI（Stateful Packet Inspection）特性
|
||||
- 实施 Default Deny 策略：默认阻断所有流量，仅放行业务明确需要的服务和网段
|
||||
|
||||
## In CTP Topic 10 (Tagging & Security)
|
||||
在 [[ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security]] 中，Pradeep 演示了 Checkpoint 在 Frankfurt Landing Zone 中的标签驱动策略集：
|
||||
|
||||
- **Policy Sets**：基于 AWS 资源标签（而非 IP 地址）的动态防火墙策略
|
||||
- **Ordered Layers**：按优先级顺序执行多层检查
|
||||
1. 地理封锁（Geo-blocking）
|
||||
2. 类型检查（Type）
|
||||
3. 业务单元隔离（BU）
|
||||
4. 产品隔离（Product）
|
||||
5. 环境隔离（Environment）
|
||||
6. 服务器角色（Server Role）
|
||||
- **Inline Layers**：基于账号编号的父子规则结构，简化跨账号规则管理
|
||||
- **Tag-Based Enforcement**：Demo 演示了 EC2 实例部署时标签缺失或错误导致流量被防火墙拦截的场景
|
||||
- **Default Deny + Inter-Product Policy**：默认阻断跨产品线通信，明确允许的通信需配置例外
|
||||
|
||||
## In CTP Topic 31
|
||||
在 [[ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones]] 中：
|
||||
- Checkpoint 作为网络隔离的执行设备，通过 SPI 阻断内部网络对 AWS 生产网段的直接访问
|
||||
- Default Deny 策略确保只有经过审批的服务和网络段能进入 Landing Zone
|
||||
- 与 SSM 安全访问方案共同构成"网络隔离 + 终端访问"的双层安全体系
|
||||
|
||||
## Key Properties
|
||||
| 属性 | 值 |
|
||||
|------|-----|
|
||||
| 类型 | Stateful Packet Inspection (SPI) Firewall |
|
||||
| 部署位置 | Network Account |
|
||||
| 策略模式 | Default Deny |
|
||||
| 用途 | 互联网边界 + Landing Zone 隔离 |
|
||||
|
||||
## Connections
|
||||
- [[Network-Segmentation]] — Checkpoint 是网络隔离的核心实施工具
|
||||
- [[ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones]]
|
||||
32
wiki/entities/ChristianDeckelman.md
Normal file
32
wiki/entities/ChristianDeckelman.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: "Christian Deckelman"
|
||||
type: entity
|
||||
tags: [AWS, Networking, WAN, CTP]
|
||||
sources: [ctp-topic-18-wide-area-networking-in-aws-cloud]
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Christian Deckelman
|
||||
|
||||
Christian Deckelman 是 Micro Focus 的 IT 网络架构师，主导 AWS 云转型计划（Cloud Transformation Programme, CTP）中的广域网（WAN）架构设计与演进规划。
|
||||
|
||||
## Role
|
||||
|
||||
- **Title**: IT 网络架构师（IT Network Architect）
|
||||
- **Organization**: [[Micro Focus]]
|
||||
- **Focus**: AWS Transit Gateway、SD-WAN、全球网络互联架构
|
||||
|
||||
## Key Contributions
|
||||
|
||||
- 设计并阐述 AWS 云环境中跨区域全球网络架构——通过 Transit Gateway (TGW) 星型拓扑连接全球 Landing Zones
|
||||
- 主导广域网演进路线图规划：从静态路由升级至 Silver Peak SD-WAN 叠加网络
|
||||
- 推动远程访问优化：Pulse VPN 迁移至 Palo Alto Prisma Access (SASE)
|
||||
|
||||
## Connections
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] ← 主讲 ← [[ChristianDeckelman]]
|
||||
- [[Micro Focus]] ← 雇主 ← [[ChristianDeckelman]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]]
|
||||
29
wiki/entities/Damian.md
Normal file
29
wiki/entities/Damian.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: "Damian"
|
||||
type: entity
|
||||
tags: [CTP, Cloud, AWS, Strategy]
|
||||
sources: [ctp-topic-20-program-demand-process-flow-and-poc-onboarding]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## Damian
|
||||
|
||||
Cloud Transformation Programme（CTP）系列学习课程讲师，主讲云转型战略与 POC 入职路径。
|
||||
|
||||
## Role
|
||||
|
||||
- **CTP Topic 20**：程序需求流程（Program Demand Process Flow）与 POC 入职（PoC Onboarding）讲师（与 Sergio 联合主讲）
|
||||
- 提及 Cloud Transformation Strategy Overview，关联 Matt 的战略优先级和整体愿景
|
||||
|
||||
## Areas of Expertise
|
||||
|
||||
- 云转型战略与整体愿景规划
|
||||
- 需求来源分析（业务案例、高层战略优先级、产品路线图）
|
||||
- POC 阶段的解决方案设计与 Design Authority 审批
|
||||
- 变更管理与组织调整
|
||||
|
||||
## Connections
|
||||
|
||||
- 与 [[Sergio]] 联合主讲 [[ctp-topic-20-program-demand-process-flow-and-poc-onboarding]]
|
||||
- 通过 [[ctp-topic-20-program-demand-process-flow-and-poc-onboarding]] 关联 [[Cloud-Transformation-Programme]]
|
||||
- 引用 [[ctp-topic-53-why-bother-with-cloud]] 的背景参考
|
||||
31
wiki/entities/Martin-Rosler.md
Normal file
31
wiki/entities/Martin-Rosler.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: "Martin Rosler"
|
||||
type: entity
|
||||
tags:
|
||||
- person
|
||||
- FinOps
|
||||
- Tagging-Standard
|
||||
- OpenText
|
||||
sources:
|
||||
- public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meeting-rec
|
||||
last_updated: 2026-04-29
|
||||
---
|
||||
|
||||
# Martin Rosler
|
||||
|
||||
OpenText/Micro Focus 云转型团队成员，FinOps 领域专家，主导 OpenText 标签标准 V2 版本的演讲和推广。
|
||||
|
||||
## Role & Contributions
|
||||
- **标签标准 V2 演讲**：Martin Rosler 在 2026 年 4 月 29 日的 Public Cloud Learning Sessions 中介绍 OpenText Tagging Standard V2，强调标准化标签对云成本优化、风险降低和效率提升的价值
|
||||
- **三大驱动**：省钱（FinOps 成本优化）、降险（快速定位技术联系人）、提效（自动化筛选）
|
||||
- **标准范围扩展**：V2 在 2023 年标准基础上，将 Kubernetes 对象和容器镜像纳入标签标准覆盖范围
|
||||
|
||||
## Key Rules & Best Practices
|
||||
- 提倡使用 Terraform IaC 自动打标
|
||||
- 建议通过检查和报告检测缺失标签
|
||||
- 强调不在标签中存储敏感数据
|
||||
- 建议对频繁变更的标签谨慎处理
|
||||
|
||||
## Connections
|
||||
- 隶属 [[Phenops-Team]]
|
||||
- 与 [[public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meeting-rec]] 相关
|
||||
23
wiki/entities/MichaelRiley.md
Normal file
23
wiki/entities/MichaelRiley.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: "Michael Riley"
|
||||
type: entity
|
||||
tags:
|
||||
- VMware
|
||||
- CTP
|
||||
- Cloud
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Michael Riley
|
||||
|
||||
VMware speaker at Cloud Transformation Programme (CTP) learning sessions.
|
||||
|
||||
## Role
|
||||
Speaker at CTP Topic 43 — VMware Cloud on AWS. Presented alongside Brian Reeves and Mike Armstrong on the VMC on AWS platform overview.
|
||||
|
||||
## Connections
|
||||
- [[VMware]] ← speaker ← [[MichaelRiley]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← presented_by ← [[MichaelRiley]]
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
39
wiki/entities/MicroFocus.md
Normal file
39
wiki/entities/MicroFocus.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: "Micro Focus"
|
||||
type: entity
|
||||
tags: [Enterprise, ITOM, Cloud-Transformation, AWS]
|
||||
sources: [ctp-topic-18-wide-area-networking-in-aws-cloud]
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Micro Focus
|
||||
|
||||
Micro Focus 是一家全球企业软件公司，专注于 IT Operations Management (ITOM)、DevOps、云转型等领域。在 AWS 云转型计划（Cloud Transformation Programme, CTP）中，Micro Focus 是主导企业，其 IT 网络架构由 Christian Deckelman 等专家设计全球广域网架构。
|
||||
|
||||
## Aliases
|
||||
|
||||
- Micro Focus
|
||||
- Micro Focus International
|
||||
|
||||
## Role in Cloud Transformation Programme (CTP)
|
||||
|
||||
- **主导企业**：Micro Focus 是 CTP 的核心推动者，涵盖从 Landing Zone 设计、网络架构到监控、备份的全套云转型方案
|
||||
- **网络架构**：由 IT 网络架构师 [[ChristianDeckelman]] 设计 AWS 全球广域网架构
|
||||
- **技术栈**：AWS Transit Gateway、Gruntwork Terraform 模块、Infoblox DNS、Pulse VPN、Checkpoint 防火墙
|
||||
|
||||
## Key CTP Topics Featuring Micro Focus
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] — WAN 架构设计
|
||||
- [[ctp-topic-25-labs-landing-zone-overview-itom-teams]] — Labs LZ 运维团队
|
||||
- [[ctp-topic-7-saas-landing-zone-design]] — SaaS Landing Zone 设计
|
||||
- [[ctp-topic-44-aws-backup-in-micro-focus]] — AWS Backup 实施
|
||||
|
||||
## Connections
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] ← 主导企业 ← [[MicroFocus]]
|
||||
- [[ChristianDeckelman]] ← 雇主 ← [[MicroFocus]]
|
||||
- [[AWS]] ← 云平台 ← [[MicroFocus]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]]
|
||||
23
wiki/entities/MikeArmstrong.md
Normal file
23
wiki/entities/MikeArmstrong.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: "Mike Armstrong"
|
||||
type: entity
|
||||
tags:
|
||||
- VMware
|
||||
- CTP
|
||||
- Cloud
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Mike Armstrong
|
||||
|
||||
VMware speaker at Cloud Transformation Programme (CTP) learning sessions.
|
||||
|
||||
## Role
|
||||
Speaker at CTP Topic 43 — VMware Cloud on AWS. Presented alongside Brian Reeves and Michael Riley on the VMC on AWS platform overview.
|
||||
|
||||
## Connections
|
||||
- [[VMware]] ← speaker ← [[MikeArmstrong]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← presented_by ← [[MikeArmstrong]]
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
30
wiki/entities/MikeOReily.md
Normal file
30
wiki/entities/MikeOReily.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: "Mike O'Reilly"
|
||||
type: entity
|
||||
tags:
|
||||
- VMware
|
||||
- CTP
|
||||
- Cloud
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Mike O'Reilly
|
||||
|
||||
Staff Cloud Solutions Architect at VMware. Primary technical presenter for VMC on AWS content at Cloud Transformation Programme (CTP) learning sessions.
|
||||
|
||||
## Role
|
||||
Staff Cloud Solutions Architect at VMware. Main technical speaker at CTP Topic 43 — VMware Cloud on AWS. Explained the joint engineering nature of VMC on AWS and demonstrated the platform capabilities.
|
||||
|
||||
## Key Technical Points
|
||||
- VMC on AWS is a jointly engineered cloud service where the VMware hypervisor runs natively on AWS bare metal servers — "not just something where VMware showed up at Amazon and dropped off a box of CDs"
|
||||
- VMC on AWS runs vSphere 8 and provides native access to AWS services with low latency
|
||||
- VMware and Amazon jointly manage the underlying infrastructure, allowing users to focus on their workloads
|
||||
- Service is available across multiple regions and availability zones globally
|
||||
|
||||
## Connections
|
||||
- [[VMware]] ← speaker ← [[MikeOReily]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← presented_by ← [[MikeOReily]]
|
||||
- [[VMware-Cloud-on-AWS]] ← explains ← [[MikeOReily]] technical architecture
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
53
wiki/entities/OpenText.md
Normal file
53
wiki/entities/OpenText.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: "OpenText"
|
||||
type: entity
|
||||
tags: [OpenText, Enterprise-Information-Management, Cloud-DevOps, Multi-Cloud, Software-Vendor]
|
||||
sources:
|
||||
- public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2
|
||||
last_updated: 2026-04-29
|
||||
---
|
||||
|
||||
## OpenText
|
||||
|
||||
OpenText 是全球领先的企业信息管理（Enterprise Information Management，EIM）软件公司，专注于帮助组织管理、发现、分析和保护非结构化数据。2023年收购 Micro Focus 后成为全球最大的企业软件公司之一。
|
||||
|
||||
## Key Facts
|
||||
|
||||
| 维度 | 说明 |
|
||||
|------|------|
|
||||
| 成立 | 1991年（加拿大滑铁卢） |
|
||||
| 上市 | NASDAQ: OTEX, TSX: OTEX |
|
||||
| 员工 | 约 23,000+ |
|
||||
| 核心业务 | 企业内容管理、CRM、业务流程管理、安全与合规 |
|
||||
| 战略方向 | 云优先（Cloud-First）、多云部署（AWS/GCP/Azure） |
|
||||
|
||||
## Multi-Cloud Architecture
|
||||
|
||||
OpenText 的产品和客户解决方案托管于三大超大规模云平台：
|
||||
|
||||
- **AWS**：主要托管区域，用于产品和客户部署
|
||||
- **Google Cloud Platform (GCP)**：特定产品线和工作负载
|
||||
- **Microsoft Azure**：混合部署和企业客户专属环境
|
||||
|
||||
## OpenText Learning Sessions
|
||||
|
||||
OpenText 内部开展了系统的"Public Cloud Learning Sessions"系列培训，涵盖：
|
||||
|
||||
- **云架构**：Landing Zone、VPC 设计、网络分段
|
||||
- **运维实践**：DR/BCP、SRE、Observability、FinOps
|
||||
- **开发运维**：CI/CD、IaC（Terraform）、容器化
|
||||
- **安全合规**：Tagging Standards、Identity Governance
|
||||
- **产品平台**：Thor Platform、Product Hub (PHT)
|
||||
|
||||
## Connections
|
||||
|
||||
- [[AWS]] ← hosted_on ← [[OpenText]]（AWS 是 OpenText 主要托管平台之一）
|
||||
- [[GCP]] ← hosted_on ← [[OpenText]]（GCP 托管 OpenText 特定产品线）
|
||||
- [[Azure]] ← hosted_on ← [[OpenText]]（Azure 混合部署环境）
|
||||
- [[MicroFocus]] ← acquired_by ← [[OpenText]]（2023 年完成收购）
|
||||
- [[public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2]] ← source ← [[OpenText]]
|
||||
- [[SRE]] ← implemented_by ← [[OpenText]]（OpenText 推行 SRE 转型）
|
||||
|
||||
## Sources
|
||||
|
||||
- [[public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2]]
|
||||
37
wiki/entities/PCGTeam.md
Normal file
37
wiki/entities/PCGTeam.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "PCG Team"
|
||||
type: entity
|
||||
tags: [CTP, Cloud, AWS, Platform]
|
||||
sources: [ctp-topic-20-program-demand-process-flow-and-poc-onboarding]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## PCG Team
|
||||
|
||||
Platform Control Group（PCG，平台控制组），是云转型计划（CTP）中负责提供云环境支持、安全策略制定及协助产品团队进行 POC 的核心技术团队。
|
||||
|
||||
## Role
|
||||
|
||||
- **云环境支持**：为产品团队提供 AWS Landing Zone 环境的部署与运维支持
|
||||
- **安全策略制定**：定义和维护云环境的安全基线与合规标准
|
||||
- **POC 协助**：在概念验证阶段为产品团队提供技术指导和架构评审
|
||||
|
||||
## Responsibilities
|
||||
|
||||
- 管理基于 Gruntwork 的 Landing Zone 参考架构
|
||||
- 提供 IaC（Terraform/Terragrunt）部署支持
|
||||
- 执行 Design Authority 审批（Gate 1），确保解决方案设计符合云原生原则
|
||||
- 定义 POC 成功标准，验证产品具备进入生产环境迁移的条件
|
||||
|
||||
## Key Deliverables
|
||||
|
||||
- 预配置的标准化 Landing Zone 环境
|
||||
- 安全策略与合规基线
|
||||
- IaC 自动化部署流水线
|
||||
- 迁移时间表与路线图
|
||||
|
||||
## Connections
|
||||
|
||||
- 为 [[ctp-topic-20-program-demand-process-flow-and-poc-onboarding]] 提供 POC 支持
|
||||
- 与 [[Gruntwork]] 合作提供 Landing Zone 参考架构
|
||||
- 通过 [[ctp-topic-1-gruntwork-landing-zone-architecture]] 提供架构基础
|
||||
37
wiki/entities/PaloAltoNetworks.md
Normal file
37
wiki/entities/PaloAltoNetworks.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "Palo Alto Networks"
|
||||
type: entity
|
||||
tags: [Security, SASE, SD-WAN, Networking, AWS]
|
||||
sources: [ctp-topic-18-wide-area-networking-in-aws-cloud]
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Palo Alto Networks
|
||||
|
||||
Palo Alto Networks 是全球领先的网络安全公司，提供包括 Prisma Access 在内的云原生安全访问服务（SASE）。在 Micro Focus AWS 云转型计划中，其 Prisma Access 产品被选定为远程访问优化方案，替代传统的 Pulse VPN。
|
||||
|
||||
## Aliases
|
||||
|
||||
- Palo Alto Networks
|
||||
- PAN
|
||||
|
||||
## Key Products Relevant to CTP
|
||||
|
||||
- **Prisma Access**: 基于云的安全访问服务（SASE），用于替代传统 VPN，提供就近接入点和统一的安全策略
|
||||
- **Next-Generation Firewall (NGFW)**: 下一代防火墙产品线
|
||||
|
||||
## Role in CTP Architecture
|
||||
|
||||
- 在 [[ctp-topic-18-wide-area-networking-in-aws-cloud]] 中被规划用于远程访问优化
|
||||
- 目标：将 Pulse VPN 迁移至 Prisma Access，通过在全球部署更多接入网关实现用户就近接入
|
||||
- 价值：显著降低访问延迟，并直接打通 SD-WAN 骨干网
|
||||
|
||||
## Connections
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] ← 供应商 ← [[PaloAltoNetworks]]
|
||||
- [[Prisma-Access]] ← 母公司 ← [[PaloAltoNetworks]]
|
||||
- [[AWS]] ← 集成平台 ← [[PaloAltoNetworks]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]]
|
||||
@@ -1,30 +1,30 @@
|
||||
---
|
||||
title: "Phenops-Team"
|
||||
type: entity
|
||||
tags:
|
||||
- team
|
||||
- FinOps
|
||||
- AWS
|
||||
sources:
|
||||
- public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123
|
||||
- public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco
|
||||
- public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meeting-reco
|
||||
last_updated: 2026-04-24
|
||||
---
|
||||
|
||||
# Phenops-Team
|
||||
|
||||
OpenText/Micro Focus 内部 FinOps 执行团队，负责费率承诺计划的实施与云成本治理。
|
||||
|
||||
## Role & Contributions
|
||||
- **标签治理**：2023 年发起云资源标签标准化项目（[[public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123]]），现已扩展至 Kubernetes 对象和容器镜像，覆盖 3,500 个云账户和 48 种 Landing Zone 类型
|
||||
- **费率承诺**：费率承诺计划（Savings Plans / Reserved Instances）的唯一实施团队（[[public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco]]）
|
||||
|
||||
## Key Rules
|
||||
- 所有承诺计划仅支持 **无预付（No Upfront）** 选项
|
||||
- 最低交易金额：**$5k/年**
|
||||
- 费率承诺实施前必须先完成 Right Sizing 分析
|
||||
|
||||
## Connections
|
||||
- 隶属 [[PCG]]（Public Cloud Governance）团队
|
||||
- 与 [[Vinay]] 等 FinOps 团队成员协作推进成本优化
|
||||
---
|
||||
title: "Phenops-Team"
|
||||
type: entity
|
||||
tags:
|
||||
- team
|
||||
- FinOps
|
||||
- AWS
|
||||
sources:
|
||||
- public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123
|
||||
- public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco
|
||||
- public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meeting-rec
|
||||
last_updated: 2026-04-29
|
||||
---
|
||||
|
||||
# Phenops-Team
|
||||
|
||||
OpenText/Micro Focus 内部 FinOps 执行团队，负责费率承诺计划的实施与云成本治理。
|
||||
|
||||
## Role & Contributions
|
||||
- **标签治理**：2023 年发起云资源标签标准化项目（[[public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123]]），现已扩展至 Kubernetes 对象和容器镜像，覆盖 3,500 个云账户和 48 种 Landing Zone 类型
|
||||
- **费率承诺**：费率承诺计划（Savings Plans / Reserved Instances）的唯一实施团队（[[public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco]]）
|
||||
|
||||
## Key Rules
|
||||
- 所有承诺计划仅支持 **无预付（No Upfront）** 选项
|
||||
- 最低交易金额：**$5k/年**
|
||||
- 费率承诺实施前必须先完成 Right Sizing 分析
|
||||
|
||||
## Connections
|
||||
- 隶属 [[PCG]]（Public Cloud Governance）团队
|
||||
- 与 [[Vinay]] 等 FinOps 团队成员协作推进成本优化
|
||||
|
||||
26
wiki/entities/Pradeep.md
Normal file
26
wiki/entities/Pradeep.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: "Pradeep"
|
||||
type: entity
|
||||
tags: ["Cloud-Transformation", "AWS", "OpenText", "Demo"]
|
||||
sources: ["ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security"]
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
Pradeep 是 OpenText/Micro Focus 云转型计划（CTP）的技术演示者，负责 Checkpoint Firewall 和 EC2 部署的实际操作演示。
|
||||
|
||||
## Contributions
|
||||
- **CTP Topic 10**（[[ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security]]）：作为本主题的演示者，Pradeep 展示了：
|
||||
- Frankfurt Landing Zone 中 Checkpoint Firewall 的策略配置界面
|
||||
- 基于标签的 Policy Sets 和 Ordered Layers 配置
|
||||
- EC2 实例部署时标签缺失或错误导致的防火墙拦截错误
|
||||
- Inline Layer 基于账号编号的父子规则结构
|
||||
|
||||
## Demonstrated Technologies
|
||||
- [[Checkpoint-Firewall]] — 标签驱动的动态防火墙策略配置
|
||||
- [[AWS-Landing-Zone]] — EC2 部署与标签应用
|
||||
- [[SCP-Security-Control-Policy]] — 标签强制执行演示
|
||||
|
||||
## Connections
|
||||
- [[Checkpoint-Firewall]] — 演示中的核心设备
|
||||
- [[ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security]]
|
||||
@@ -35,6 +35,19 @@ last_updated: 2026-05-06
|
||||
- Pulse Secure VPN
|
||||
- Pulse VPN Client
|
||||
|
||||
## Role in CTP Architecture
|
||||
|
||||
- **现状**: 在 [[ctp-topic-7-saas-landing-zone-design]] 中作为 SAS LZ 标准远程访问 VPN
|
||||
- **演进**: 在 [[ctp-topic-18-wide-area-networking-in-aws-cloud]] 中规划迁移至 [[PaloAltoNetworks]] [[Prisma-Access]]（SASE 方案）
|
||||
|
||||
## Connections
|
||||
|
||||
- [[ctp-topic-7-saas-landing-zone-design]] — SAS LZ 远程接入方案
|
||||
- [[ctp-topic-35-aws-landing-zone-design-refresher-saas-labs]] — 网络分段策略变更（Checkpoint 重新路由入站流量）
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] — 演进目标：迁移至 Prisma Access
|
||||
- [[Prisma-Access]] ← 替代 ← [[Pulse-VPN]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-7-saas-landing-zone-design]]
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]]
|
||||
|
||||
36
wiki/entities/Pushka.md
Normal file
36
wiki/entities/Pushka.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: "Pushka"
|
||||
type: entity
|
||||
tags: []
|
||||
sources:
|
||||
- ctp-topic-45-automatic-ip-address-allocation-with-ipam
|
||||
- ctp-topic-61-workload-vpc-provision-with-ipam-automation
|
||||
last_updated: 2026-04-24
|
||||
---
|
||||
|
||||
## Pushka
|
||||
|
||||
Principal SRE，Cloud Transformation Programme (CTP) 的核心讲师之一，IPAM 与 VPC 自动化方案的发起人和主要演示者。
|
||||
|
||||
## Role
|
||||
|
||||
- **CTP Topic 45**：IPAM 自动分配 IP 地址机制详解——介绍 Infoblox NIOS 如何替代 Excel 手工管理，实现声明式 VPC IP 地址供给
|
||||
- **CTP Topic 61**：Workload VPC 完整自动化供给方案——展示端到端 VPC 供给流程，包括 CIDR 审批阈值和 AZ ID 等增强功能
|
||||
|
||||
## Areas of Expertise
|
||||
|
||||
- Infoblox NIOS IPAM 平台与 AWS VPC 供给集成
|
||||
- 声明式 IaC 自动化（YAML 配置驱动）
|
||||
- AWS 多账号网络架构
|
||||
- IP 地址管理生命周期
|
||||
|
||||
## Key Quotes
|
||||
|
||||
> "We don't need to worry about IP address. If it's beyond IP address is 22 or greater, then only we need to take the approval." — CIDR 审批阈值说明
|
||||
|
||||
> "So we just need to put the information at the right place and everything will work." — IPAM 自动化核心理念
|
||||
|
||||
## Connections
|
||||
|
||||
- 通过 [[ctp-topic-45-automatic-ip-address-allocation-with-ipam]] 介绍 IPAM 自动化机制
|
||||
- 通过 [[ctp-topic-61-workload-vpc-provision-with-ipam-automation]] 展示 VPC 供给完整应用
|
||||
@@ -1,28 +1,29 @@
|
||||
---
|
||||
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 架构
|
||||
---
|
||||
title: "Sankar Gopov"
|
||||
type: entity
|
||||
tags: []
|
||||
sources:
|
||||
- ctp-topic-19-configuring-dns-within-aws-lzs
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## 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 架构
|
||||
|
||||
28
wiki/entities/Sergio.md
Normal file
28
wiki/entities/Sergio.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: "Sergio"
|
||||
type: entity
|
||||
tags: [CTP, Cloud, AWS, DevOps]
|
||||
sources: [ctp-topic-20-program-demand-process-flow-and-poc-onboarding]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## Sergio
|
||||
|
||||
Cloud Transformation Programme（CTP）系列学习课程讲师，主讲云转型项目的需求流程与 POC 入职路径。
|
||||
|
||||
## Role
|
||||
|
||||
- **CTP Topic 20**：程序需求流程（Program Demand Process Flow）与 POC 入职（PoC Onboarding）讲师（与 Damian 联合主讲）
|
||||
- 专注于云迁移的治理框架、需求管理与概念验证实施路径
|
||||
|
||||
## Areas of Expertise
|
||||
|
||||
- 企业级云迁移需求管理与优先级排序
|
||||
- 概念验证（POC）实施路径与 Gate Process 审批流程
|
||||
- 基于 Gruntwork 的 Landing Zone 架构实践
|
||||
- IaC（Terraform/Terragrunt）自动化部署
|
||||
|
||||
## Connections
|
||||
|
||||
- 与 [[Damian]] 联合主讲 [[ctp-topic-20-program-demand-process-flow-and-poc-onboarding]]
|
||||
- 通过该课程与 [[ctp-topic-57-product-backlog-managing-demand]] 共享需求管理主题
|
||||
36
wiki/entities/SilverPeak.md
Normal file
36
wiki/entities/SilverPeak.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: "Silver Peak"
|
||||
type: entity
|
||||
tags: [SD-WAN, Networking, WAN, Overlay]
|
||||
sources: [ctp-topic-18-wide-area-networking-in-aws-cloud]
|
||||
last_updated: 2026-05-07
|
||||
---
|
||||
|
||||
## Silver Peak
|
||||
|
||||
Silver Peak 是一家专注于 SD-WAN（Software-Defined Wide Area Network）解决方案的技术公司，2020年被 HP (Hewlett Packard Enterprise) 收购。其 SD-WAN 产品作为叠加网络（Overlay Network）解决方案，计划在 Micro Focus AWS 云转型中被引入，用于替代静态路由实现动态路径选择和自动化流量调度。
|
||||
|
||||
## Aliases
|
||||
|
||||
- Silver Peak
|
||||
- Silver Peak Systems
|
||||
|
||||
## Key Product
|
||||
|
||||
- **Silver Peak SD-WAN**: 软件定义广域网解决方案，通过在 AWS 中部署虚拟 SD-WAN 设备，实现动态路径选择和自动化流量调度
|
||||
|
||||
## Role in CTP Architecture
|
||||
|
||||
- 在 [[ctp-topic-18-wide-area-networking-in-aws-cloud]] 中被规划为 Transit Gateway 架构的演进方案
|
||||
- 目标：解决 TGW 间静态路由在 DR 场景下需要人工干预的局限性
|
||||
- 部署模式：在 AWS 中部署虚拟 SD-WAN 设备作为叠加网络层
|
||||
|
||||
## Connections
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]] ← 供应商 ← [[SilverPeak]]
|
||||
- [[SD-WAN]] ← 提供商 ← [[SilverPeak]]
|
||||
- [[AWS]] ← 部署平台 ← [[SilverPeak]]
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-18-wide-area-networking-in-aws-cloud]]
|
||||
18
wiki/entities/SteveJarman.md
Normal file
18
wiki/entities/SteveJarman.md
Normal file
@@ -0,0 +1,18 @@
|
||||
---
|
||||
title: "Steve Jarman"
|
||||
type: entity
|
||||
tags: ["Cloud-Transformation", "AWS", "OpenText"]
|
||||
sources: ["ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security"]
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
Steve Jarman 是 OpenText/Micro Focus 云转型计划（CTP）的核心技术演讲者之一，在 AWS Landing Zone 主题系列中多次主讲。
|
||||
|
||||
## Contributions
|
||||
- **CTP Topic 10**（[[ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security]]）：与 Pradeep 联合主讲，深入阐述 AWS Landing Zone 的数据收集、标签体系及基于标签的云原生安全架构。Steve 强调在将资产迁移至云之前必须先收集机器信息、理解迁移范围、应用正确标签，以确保云环境的安全 posture 正确。
|
||||
|
||||
## Connections
|
||||
- [[AWS-Landing-Zone]] — 核心演讲主题
|
||||
- [[Cloud-Transformation-Programme]] — 云转型计划演讲者
|
||||
- [[ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security]]
|
||||
20
wiki/entities/Vinaya.md
Normal file
20
wiki/entities/Vinaya.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Vinaya"
|
||||
type: entity
|
||||
tags: [Product-Teams, Self-Healing, SRE, Cloud-Transformation]
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Vinaya 是内部产品团队成员，在云转型项目中活跃参与 SRE 实践推广。在 CTP Topic 30（Managing Change）会议中，Vinaya 提议各产品组分享现有的 Self-Healing 实践案例，由 SRE 团队协助在监控产品中落地。
|
||||
|
||||
## Role in Cloud Transformation
|
||||
|
||||
- **Self-Healing 推广者**：Vinaya 认识到 Self-Healing（基于 ML 的自动化监控系统）是未来演进方向，积极推动产品团队间的经验分享
|
||||
- **SRE 协作桥梁**：作为产品团队代表，与 SRE 团队（由 Brendan Starnig 领导）建立协作关系
|
||||
- **自动化倡导者**：支持通过机器学习驱动的自动化监控系统，基于告警趋势自动决策和缓解问题
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-30-managing-change]]
|
||||
33
wiki/entities/cloud-transformation-programme.md
Normal file
33
wiki/entities/cloud-transformation-programme.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: "Cloud Transformation Programme (CTP)"
|
||||
type: entity
|
||||
entity_type: Project
|
||||
tags:
|
||||
- Cloud-Transformation
|
||||
- OpenText
|
||||
- CTP
|
||||
- AWS
|
||||
sources:
|
||||
- ctp-topic-65-tracing-the-value-delivered-in-cloud-transformation
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
OpenText 的 Cloud Transformation Programme（云转型计划，简称 CTP）是一个跨多个业务单元的系统性云迁移与转型项目，旨在将传统本地基础设施迁移至 AWS 等公有云平台，并通过 [[Lean]] 方法论和 [[Scaled Agile]] 框架实现价值最大化交付。
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Value Stream]]：CTP 的工作组织方式
|
||||
- [[Weighted Shortest Job First (WSJF)]]：CTP 工作的优先级排序方法
|
||||
- [[Cost of Delay (CoD)]]：CTP 价值评估的核心指标
|
||||
|
||||
## Related Sources
|
||||
|
||||
- [[CTP Topic 65 Tracing the Value Delivered in Cloud Transformation]]
|
||||
- （其他 CTP Topic source pages，见 index.md）
|
||||
|
||||
## Aliases
|
||||
- CTP
|
||||
- Cloud Transformation Programme
|
||||
- 云转型计划
|
||||
Reference in New Issue
Block a user