Auto-sync: wiki-ingest 3 sources (2026-04-16)
This commit is contained in:
@@ -11,7 +11,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 18_ Wide Area Networking in AWS Cloud.mp4"
|
||||
audio-source: ""
|
||||
status: summarized
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 18 Wide Area Networking in AWS Cloud
|
||||
@@ -20,7 +20,7 @@ status: summarized
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 19_ Configuring DNS within AWS LZs.mp4"
|
||||
audio-source: ""
|
||||
status: summarized
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 19 Configuring DNS within AWS LZs
|
||||
@@ -20,7 +20,7 @@ status: summarized
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 22_ Global DNS service offerings.mp4"
|
||||
audio-source: ""
|
||||
status: summarized
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 22 Global DNS service offerings
|
||||
@@ -19,7 +19,7 @@ status: summarized
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -1,17 +1,17 @@
|
||||
---
|
||||
title: "CTP Topic 31 Network segregation and secure access to the new AWS landing zones"
|
||||
title: CTP Topic 31 Network segregation and secure access to the new AWS landing zones
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/08_Networking"
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- AWS
|
||||
- Network-Security
|
||||
- Landing-Zone
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 31_ Network segregation and secure access to the new AWS landing zones.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 31_ Network segregation and secure access to the new AWS landing zones.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 31 Network segregation and secure access to the new AWS landing zones
|
||||
@@ -26,7 +26,16 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## Network Segregation and Secure Access to AWS Landing Zones
|
||||
|
||||
The primary driver for this initiative is to address security concerns related to internal systems accessing production workloads in the new AWS landing zones. Currently, on-prem systems and VPN users have access due to shared network configurations, raising security and compliance issues. The goal is to segregate network access while maintaining necessary access for run teams.
|
||||
|
||||
The proposed solution involves two main parts: network segregation and secure access. Network segregation will be implemented using checkpoints to control server-to-server communications and block direct access from internal networks to AWS segments. *The SPI features will be enabled with default deny enabled and allowances made for require services and network segments into the landing zones.* Secure access will be facilitated through AWS Systems Manager (SSM), which provides remote access via a browser-based session or AWS CLI, eliminating the need for VPN.
|
||||
|
||||
Authenticated users will assume roles granting access to the SSM agent on the target EC2 instance, leveraging existing access controls. This approach offers enhanced security with two-factor authentication and a secure connection within the AWS network. While this solution is considered temporary or a backup until SD-WAN is implemented, it offers cost and speed advantages by removing reliance on third-party management. *SSM gives users remote access via a browser based session.* The implementation is in progress, with testing planned to address urgent security risks associated with production workloads on AWS landing zones.
|
||||
|
||||
Concerns were raised about the SSM agent's presence in all AWS-derived AMIs, with some suggesting it may need explicit installation on certain systems. The long-term goal is to move towards infrastructure as code to minimize console access and enhance security, with break-glass access reserved for emergencies. The current solution doesn't address credential theft but isolates the network. A question was raised about how users with multiple accounts for different roles can use SSM, as the current setup is designed for individual accounts. This edge case will be examined further.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: CTP Topic 31 Network segregation and secure access to the new AWS landing zones
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- AWS
|
||||
- Network-Security
|
||||
- Landing-Zone
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 31_ Network segregation and secure access to the new AWS landing zones.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 31 Network segregation and secure access to the new AWS landing zones
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 31_ Network segregation and secure access to the new AWS landing zones.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,17 +1,17 @@
|
||||
---
|
||||
title: "CTP Topic 36 SendGrid as an email service"
|
||||
title: CTP Topic 36 SendGrid as an email service
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/08_Networking"
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- SendGrid
|
||||
- Email
|
||||
- AWS
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 36_ SendGrid as an email service.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 36_ SendGrid as an email service.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 36 SendGrid as an email service
|
||||
@@ -26,7 +26,18 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## Cloud Transformation Program: SendGrid Email Service & Cyber Suite Standards
|
||||
|
||||
The Cloud Transformation Program session covered the adoption of SendGrid as a standard email service and provided an update on Cyber Suite standards. Rejoy Ganapati and Rajiv presented SendGrid, while Yu-Yan provided the Cyber Suite update.
|
||||
|
||||
SendGrid is being adopted as the standard email service for both classic and new landing zones, replacing the existing semantic message gateway and SES solutions. The existing semantic message gateway has security concerns because it relays mail to the public internet through port 25, which is not secure. Additionally, the relay servers are not compatible with cloud environments and are hosted on a soon-to-be-decommissioned on-premises network. The current SES setup has a limitation of only 50 recipients per message.
|
||||
|
||||
SendGrid overcomes these issues by allowing up to 1,000 recipients per message and being fully cloud-compatible. *Almost 30 billion emails per month customers are already used across the whole country.* It offers real-time monitoring logs, two-factor authentication, and end-to-end encryption using TLS. The support plan covers 5 million emails per month. Two architectures are available: direct sending to SendGrid (requires TLS) and relaying via servers for applications lacking TLS support. *We were looking for the maximum number of recipients per message.* Data flow involves relay servers in various locations (London, India, Tokyo, etc.) sending mail through private circuits to a US-based data center for processing.
|
||||
|
||||
Key configuration requirements for direct sending include using the software.microcopy.com domain, connectivity to smtp.sendgrid.net on port 587, and TLS enablement. Domain-specific email blocking is not supported, and the sender email address must use the software.microcopy.com domain. Email logs are retained for seven days, and API keys are rotated every 180 days for security. SPF and DKIM records are essential for valid email sending to avoid emails landing in junk folders or being rejected.
|
||||
|
||||
Yu-Yan from PSAC provided an update on Cyber Suite standards, presenting an updated version of the standard Cyber Suite documentation. The updated documentation includes a list of Cyber Suites considered standard by different industry standards like FIPS, Java, Golang, Node.js, and OpenCel for CNC++. An optional Cyber Suite is available for backward compatibility, but it includes CBC (Cipher Block Chaining) which is considered weak. For more choices, products can select cyphers from different portions, including K exchange, authentication, encryption, and hash. It is recommended that products using cyphers outside the standard and optional suites be reviewed by the PSAC team.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: CTP Topic 36 SendGrid as an email service
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- SendGrid
|
||||
- Email
|
||||
- AWS
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 36_ SendGrid as an email service.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 36 SendGrid as an email service
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 36_ SendGrid as an email service.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: "CTP Topic 43 VMware Cloud on AWS"
|
||||
title: CTP Topic 43 VMware Cloud on AWS
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/08_Networking"
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- VMware
|
||||
- AWS
|
||||
@@ -10,9 +10,9 @@ tags:
|
||||
- Hybrid-Cloud
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 43_ VMware Cloud on AWS.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 43_ VMware Cloud on AWS.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 43 VMware Cloud on AWS
|
||||
@@ -27,7 +27,27 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## VMware Cloud on AWS: An Introduction
|
||||
|
||||
The Cloud Transformation Office program hosted a session on VMware Cloud on AWS (VMC on AWS), presented by Brian Reeves, Michael Riley, and Mike Armstrong from VMware. The session aimed to provide an understanding of VMC on AWS and its potential benefits for organizations.
|
||||
|
||||
VMware and AWS partnered to enable vSphere workloads on Amazon's backend servers, offering a middle ground for organizations not ready for a full native cloud migration. *This allows applications to move back and forth in seconds.* VMC on AWS provides access to AWS services and aims to be economical. The presenters covered use cases, cost benefits, and a technical demonstration of the platform.
|
||||
|
||||
Mike O'Reilly, a staff cloud solutions architect at VMware, explained that VMC on AWS is a jointly engineered cloud service where the VMware hypervisor is natively installed on AWS hardware. *This is not just something where VMware showed up at Amazon and dropped off a box of CDs.* VMC on AWS is running vSphere 8 and provides access to AWS services with low latency. VMware and Amazon manage the underlying infrastructure, allowing users to focus on their workloads. The service is available across multiple regions and availability zones globally.
|
||||
|
||||
Key features and benefits include:
|
||||
* Same toolset as on-premises environments.
|
||||
* Integration with AWS services.
|
||||
* On-demand scalability.
|
||||
* Any-to-any vSphere migration using HCX.
|
||||
* Various use cases such as next-generation application development, cloud migrations, virtual desktops, and disaster recovery.
|
||||
|
||||
The service is available in numerous regions worldwide and has various certifications for security and compliance. The infrastructure is built on i3.metal and i3en.metal server hosts from Amazon, which are organized into clusters within availability zones and regions. Stretched clusters across availability zones are also possible for increased resilience.
|
||||
|
||||
A live demo showcased the VMware Cloud service portal, including the Developer Center with API Explorer for various APIs. The demo also showed how to create a new software-defined data center (SDDC) and manage the environment through vCenter, similar to on-premises setups. A follow-me help button provides access to VMware engineers for assistance.
|
||||
|
||||
Brian Reeves discussed the economics of VMC on AWS, highlighting that VMware sells an entire host, enabling over-provisioning and cost reduction. VMC on AWS offers a 27% cost saving compared to going to a regular cloud. The cloud economics team can perform a Total Cost of Ownership (TCO) calculation to compare costs with on-premises or other hyperscalers.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: CTP Topic 43 VMware Cloud on AWS
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- VMware
|
||||
- AWS
|
||||
- Networking
|
||||
- Hybrid-Cloud
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 43_ VMware Cloud on AWS.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 43 VMware Cloud on AWS
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 43_ VMware Cloud on AWS.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,17 +1,17 @@
|
||||
---
|
||||
title: "CTP Topic 45 Automatic IP address allocation with IPAM"
|
||||
title: CTP Topic 45 Automatic IP address allocation with IPAM
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/08_Networking"
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- AWS
|
||||
- IPAM
|
||||
- Networking
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 45_ Automatic IP address allocation with IPAM.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 45_ Automatic IP address allocation with IPAM.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 45 Automatic IP address allocation with IPAM
|
||||
@@ -26,7 +26,22 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## Automatic IP Address Allocation Using IPAM
|
||||
|
||||
IPAM (IP address management) provides the ability to effectively manage, control, monitor, and assign IP address space within a company. It automates IP address management tasks in a centralized and easily accessible manner. Currently, IP addresses are managed in Excel sheets, which is inefficient. Info blocks NIOA appliance provides IPAM functionality as a seamless extension of distributed grid framework, DNS, and DHCP with a unified management console.
|
||||
|
||||
The current architecture involves a grid master and various AWS cloud accounts. API calls are made to interact with the grid. Extensible attributes have been defined for cloud usage, including space owner, company, subnet name, compartment type, and status.
|
||||
|
||||
The current VPC provisioning approach involves collecting data from the business unit (BU) regarding their IP address needs. The SRE team raises a request to the network team, who calculates the optimal CIDR range and updates a spreadsheet. The SRE team then prepares a YAML file to provision the VPC. *Managing the IP address in a spreadsheet takes time and it's not a good approach.*
|
||||
|
||||
The new approach automates subnet calculation using Infoblox NIOS. If the requested network address is less than 24, the VPC module is run. If it is more than 24, mandatory approval from the network team is required. The key difference is that IP addresses are no longer requested from the network team, and the network.yml file is not prepared manually. NIOS automatically provides the next available IP address.
|
||||
|
||||
The new YAML file includes a new info blocks block with business contact, engineering contact, and date. It does not contain CIDR subnet IP addresses. Instead, it specifies the desired subnet size (e.g., /22). A parent cider is included, which is a constant value per region. The VPC name is now included in the YAML file, allowing for multiple VPCs.
|
||||
|
||||
The new system is fully automated, querying info box to get the next available block and provision accordingly. It aims to reduce handoffs and provide a single source of truth. The system is backward compatible, meaning existing VPC configurations using the old YAML file will continue to work. The goal is for any new VPC that we don't have to engage the network team every time we want to create a VPC with the subnets.
|
||||
|
||||
The implementation also allows for specifying availability zone IDs for subnets. *We are not asking for IP address from the network team.* The system also supports de-provisioning, where destroying a VPC will remove all entries from the IPAM grid. Safeguards are in place to prevent accidental deletion of VPCs, such as requiring a special flag in Terragrant.htl.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: CTP Topic 45 Automatic IP address allocation with IPAM
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- AWS
|
||||
- IPAM
|
||||
- Networking
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 45_ Automatic IP address allocation with IPAM.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 45 Automatic IP address allocation with IPAM
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 45_ Automatic IP address allocation with IPAM.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: "CTP Topic 61 Workload VPC provision with IPAM Automation"
|
||||
title: CTP Topic 61 Workload VPC provision with IPAM Automation
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/08_Networking"
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- AWS
|
||||
- VPC
|
||||
@@ -10,9 +10,9 @@ tags:
|
||||
- Automation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 61_ Workload VPC provision with IPAM Automation.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 61_ Workload VPC provision with IPAM Automation.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 61 Workload VPC provision with IPAM Automation
|
||||
@@ -27,7 +27,16 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## IPAM and Workload VPC Provisioning Automation
|
||||
|
||||
Pushka, a principal SRE, presented an overview of IPAM (IP Address Management) and its integration with workload VPC provisioning, including recent enhancements. The session covered the benefits of IPAM, its architecture, and a demo of the automated VPC provisioning process.
|
||||
|
||||
IPAM automates IP address management, eliminating manual intervention and reducing errors. It uses Infoblox grid, which consists of containers and IP addresses, and includes extensible attributes (metadata) for each IP address, such as owner, company, and status. The current workload VPC approach is automated, using IPAM YAML files that specify parameters like business contact, engineering contact, and parent CIDR. *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.* Availability Zone IDs (az id) are used instead of names (az name) to avoid inconsistencies.
|
||||
|
||||
Enhancements include provisioning multiple VPCs, email notifications, additional CIDR support, non-routable IP address support (using 10.2.0.0/16), and approval requirements for /22 or smaller CIDR blocks. Overlapping IP addresses are prevented by Infoblox grid, which manages all IP addresses. A demo showed how to provision a VPC, including the justification process for larger CIDR blocks. *So we just need to put the information at the right place and everything will work.*
|
||||
|
||||
The approval process for CIDR blocks smaller than /22 involves submitting a justification that is reviewed by the network team. If approved, the VPC provisioning proceeds; otherwise, it fails. Email notifications are sent to the user and the network team throughout the process. Infoblox maintains a list of provisioned IPs against each AWS account, accessible via the Infoblox grid interface. The Infoblox architecture includes a master database in a Houston data center, with redundant systems for DNS, NTP, and DHCP services.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: CTP Topic 61 Workload VPC provision with IPAM Automation
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- AWS
|
||||
- VPC
|
||||
- IPAM
|
||||
- Automation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 61_ Workload VPC provision with IPAM Automation.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 61 Workload VPC provision with IPAM Automation
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 61_ Workload VPC provision with IPAM Automation.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,17 +1,17 @@
|
||||
---
|
||||
title: "CTP Topic 69 Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A"
|
||||
title: CTP Topic 69 Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/08_Networking"
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- VMware
|
||||
- Migration
|
||||
- VMWare-Cloud-AWS
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 69_ Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 69_ Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 69 Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A
|
||||
@@ -26,7 +26,14 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> The session covers best practices for migrating on-premises virtual machines to VMware Cloud on AWS, based on experience and consultant support from VMware. It includes an overview of VMware Cloud, its deployment, security considerations, migration practices, automation, and a live demo.
|
||||
|
||||
The VMware Cloud environment is hosted on AWS infrastructure, offering services like vSphere, connectivity, and firewalls. It enables seamless migration of workloads with minimal changes, saving time and reducing downtime. *It hardly takes a VM migration with few minutes, which will enable them operated in the cloud infrastructure.* Benefits include easy deployment, interoperability, and infrastructure on demand. The architecture involves connecting the on-premises cloud to the Frankfurt AWS region via Direct Connect, utilizing a virtual transit gateway for seamless migration connectivity. The infrastructure includes compute and management gateways, with the latter managed by VMware and AWS.
|
||||
|
||||
Network and security considerations include using segments (VLANs), VPNs, NATs, and firewalls. The setup involves connecting customer premises to the VMware cloud through BGP protocol and a virtual gateway. HCX (Hybrid Cloud Extender) facilitates multi-cloud management, allowing viewing of on-premises vSphere from STDC and vice versa. Account structure involves VMware owning the STDC, with clusters and ESX nodes (EC2 bare metal instances) managed by VMware. Cost implications involve data transfer charges, with costs varying based on the number of STDCs and regions. *Anything which leaves definitely attracts cost.* Workload migration involves assessing compute sizing, configuration, and network requirements. Pre- and post-migration activities are automated, gathering metrics and configuring settings. HCX manager is used for seamless migrations, supporting up to 200 VMs per iteration.
|
||||
|
||||
Two migration methods are used: the UI method provided by VMware Cloud and a solution developed by the CCOE team using over-sell scripts. The UI method is straightforward, while the CCOE solution uses an input file with VM details for automated migration. Post-migration, VMs are managed through a Brown to Manage system, integrating SMACS suite and HCMX with a content pack for user management. The demo showcased preparing an input file, accessing HCX appliance in vCenter, configuring interconnect settings, and initiating migration. Post-migration tasks include ensuring proper network adapter connections and enabling tags for end-user access.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: CTP Topic 69 Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/08_Networking
|
||||
tags:
|
||||
- VMware
|
||||
- Migration
|
||||
- VMWare-Cloud-AWS
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 69_ Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 69 Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 69_ Best Practices for Migrating On-Premises (IOD) Virtual Machines to VMware Cloud on A.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 08_Networking
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
Reference in New Issue
Block a user