Auto-sync: wiki-ingest 3 sources (2026-04-16)
This commit is contained in:
@@ -8,7 +8,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 10_ AWS Landing Zone (LZ) Data Collection, Tagging _ Related Security.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 10 AWS Landing Zone (LZ) Data Collection, Tagging Related Security
|
||||
@@ -23,7 +23,18 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## AWS Landing Zones: Data Collection, Tagging, and Security
|
||||
|
||||
The session focuses on AWS landing zones, specifically data collection, tagging, and related security measures, including a demo. The primary goal is to explain tagging, its purpose, and how it's changing security practices.
|
||||
|
||||
A high-level review of deploying a new landing zone covers OUs, SCPs (security control policies), and resource tagging. The discussion highlights how firewalls interact with tagged resources and the advantages over traditional firewall rules. Pradeep demonstrates the firewall and its policy sets, along with an EC2 deployment example to illustrate policy enforcement.
|
||||
|
||||
*We ask a lot of questions so that we can then turn around and make sure we're putting the appropriate posture in the cloud and that we're protecting the resources appropriately.* A new strategy using layers of OUs to examine tags ensures correct tagging and necessary security controls. For instance, an ADM user cannot alter their tag to ITOM. SCPs are deny policies that grant resource access based on tag matching. When collecting machine information, the focus is on understanding what's being moved to the cloud and applying appropriate tags.
|
||||
|
||||
An example tag base includes machine names, owners (preferably PDLs), types (e.g., R&D), business units, products, environments (e.g., production), server roles, accounts, and app IDs. A layered approach is used in the firewall policies, starting with geo-blocking and progressing through type, BU, product, environment, and role checks. *Inter product is not allowed. Inter product is communications allowed.* The introduction of inline layers checks account numbers, streamlining rule management and automation. Tagging enables dynamic cloud environments without constant firewall adjustments, as policies are tag-based rather than IP-based.
|
||||
|
||||
The demo shows a Checkpoint firewall setup in the Frankfurt landing zone, reviewing tags and policy configurations. It demonstrates deploying an EC2 instance with tags and the errors that occur when tags are missing or incorrect. SCPs control which tags can be used in specific accounts. The ordered layer requires traffic to pass through each layer sequentially, while the inline layer uses a parent-child rule structure based on account numbers.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 20_ Program demand process flow and PoC onboarding.mp4"
|
||||
audio-source: ""
|
||||
status: summarized
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 20 Program demand process flow and PoC onboarding
|
||||
@@ -20,7 +20,7 @@ status: summarized
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**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 23_ Introduction to the Technical Architecture team and function.mp4"
|
||||
audio-source: ""
|
||||
status: summarized
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 23 Introduction to the Technical Architecture team and function
|
||||
@@ -19,7 +19,7 @@ status: summarized
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 30_ Managing change.mp4"
|
||||
audio-source: "/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 30_ Managing change.mp3"
|
||||
transcript-source: "/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 30_ Managing change.txt"
|
||||
status: summarized
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 30 Managing change
|
||||
@@ -20,7 +20,7 @@ status: summarized
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** ✅ 已完成
|
||||
**Status:** ✅ 已完成（Gemini 摘要）
|
||||
|
||||
**讲者:** Brendan Starnig (SRE Function Lead, Platform Engineering)
|
||||
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
---
|
||||
title: "CTP Topic 4 Using Agile to run the Cloud Transformation Program"
|
||||
title: CTP Topic 4 Using Agile to run the Cloud Transformation Program
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Agile
|
||||
- Cloud-Transformation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 4_ Using Agile to run the Cloud Transformation Program.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 4_ Using Agile to run the Cloud Transformation Program.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 4 Using Agile to run the Cloud Transformation Program
|
||||
@@ -25,7 +25,16 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## Agile Framework and Cloud Transformation Program
|
||||
|
||||
Heather Norris, project manager on the cloud transformation program, discussed the agile principles and methodologies used, covering the journey from its start to current practices, and offering tips for future improvements. Key aspects of agile include team collaboration and communication. The presentation covered agile frameworks, ceremonies (meetings), plan and board activities, and key takeaways.
|
||||
|
||||
The program initially used the Scrum framework with two-week sprints, which included product backlogs, sprint planning, retrospectives, reviews, and daily scrums. *The big problem with Scrum, in my opinion, is that you can't make changes throughout the sprints, we are not advised to.* Due to the inevitable changes in the program, a transition to a Kanban structure with continuous flow was necessary. Kanban allows changes at any time and focuses on continuous delivery rather than releases at the end of each sprint. The current framework is a hybrid, primarily using Kanban but retaining fixed ceremonies from Scrum, specifically daily stand-ups and retrospectives.
|
||||
|
||||
Daily stand-ups are designed to quickly inform everyone of what's going on in the team. These sessions should be brief (15-30 minutes) and focus on updates reflected in the planner board, answering what was completed yesterday, what's being done today, and any blockers. Retrospectives are important for rapid feedback and improving the development culture, helping to understand what's working well and what's not. *Agile is all about getting that rapid feedback to make the product and make the, you know, the development culture better.* Action items with owners should be detailed to drive improvements.
|
||||
|
||||
The Microsoft Planner board is used to manage projects, add user requirements, and centralize information. The board follows a Kanban structure with columns for backlog, to do, in progress, program key decisions, and icebox. Key practices include assigning a single owner to each task, even with multiple contributors, and clearly defining roles such as oversight. Linking dependent cards and using priorities and due dates are also crucial. Changes to prioritization, dates, owners, or progress should always be communicated with comments on the cards.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: CTP Topic 4 Using Agile to run the Cloud Transformation Program
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Agile
|
||||
- Cloud-Transformation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 4_ Using Agile to run the Cloud Transformation Program.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 4 Using Agile to run the Cloud Transformation Program
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 4_ Using Agile to run the Cloud Transformation Program.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,14 +1,14 @@
|
||||
---
|
||||
title: "CTP Topic 41 NFR’s and Error Budgets"
|
||||
title: CTP Topic 41 NFR’s and Error Budgets
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- uncategorized
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 41_ NFR’s and Error Budgets.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 41_ NFR’s and Error Budgets.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 41 NFR’s and Error Budgets
|
||||
@@ -23,7 +23,24 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## NFRs and Error Budgets
|
||||
|
||||
Brendan Standing, head of SRE at Micro Focus, discusses non-functional requirements (NFRs) and error budgets in the context of cloud and agile development. The goal is to drive collaboration between product groups and operations to meet customer expectations, ensure operational requirements in an agile manner, and understand error budget boundaries to deliver features quickly and reliably.
|
||||
|
||||
An NFR is a criterion used to judge a system's operation, while an error budget is the maximum time a system can fail without consequences. Historically, NFRs in on-premise data centers were complex and slowed progress, but the focus now is on agile implementation in the cloud.
|
||||
|
||||
The cloud landscape shifts ownership, with cloud providers handling infrastructure as a service, platform as a service, or software as a service. AWS's shared responsibility model means the company no longer manages data centers but must architect and manage services in the cloud to meet NFRs. *We want to drive collaboration across our product groups and operations to ensure our obligation to our customers.*
|
||||
|
||||
An epic for NFR templates aims to integrate NFRs into sprint backlogs, ensuring consideration for any major change. NFRs should be more prescriptive in the cloud, leveraging cloud-native services. Examples include specific backup procedures using AWS backup with defined cadences and testing, as well as DR planning with quarterly testing and infrastructure as code.
|
||||
|
||||
Error budgets measure the amount of unreliability a service can have before impacting customers. Developers can take more risks if within budget but must make safer choices if not. Error budgets normalize failure and bridge the gap between development and operations. They are derived from service level objectives (SLOs) and measured by service level indicators (SLRs).
|
||||
|
||||
SLRs are quantifiable measures of reliability, SLOs define how a service should perform, and SLAs are customer-level agreements. Error budget equals one less the availability SLO. For example, with a 99.9% uptime SLO, the error budget is 0.1%. *Error budgets normalize failure as part of the development process.*
|
||||
|
||||
Perfect availability is 100%, and the error budget falls between the SLO and 100%. Monitoring capabilities are crucial to measure whether error budgets are met or exceeded. Smaller iterations of changes and well-tested deployments are essential. Monitoring should quickly show whether error budgets are underutilized or exceeded.
|
||||
|
||||
Chaos engineering involves intentionally causing faults to test system resilience and ensure NFRs are met. NFRs should be testable and automated. The next steps involve working with product groups to integrate NFRs into backlogs, refine them, and develop SLOs.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: CTP Topic 41 NFR’s and Error Budgets
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- uncategorized
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 41_ NFR’s and Error Budgets.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 41 NFR’s and Error Budgets
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 41_ NFR’s and Error Budgets.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,16 +1,16 @@
|
||||
---
|
||||
title: "CTP Topic 53 Why bother with Cloud"
|
||||
title: CTP Topic 53 Why bother with Cloud
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Cloud
|
||||
- Strategy
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 53_ Why bother with Cloud_.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 53_ Why bother with Cloud_.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 53 Why bother with Cloud
|
||||
@@ -25,7 +25,37 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## Cloud Transformation Program Update
|
||||
|
||||
The Cloud Transformation Program aims to consolidate infrastructure, reduce costs, and enable innovation across Micro Focus. The program presented its progress and plans to stakeholders, emphasizing cost reduction and increased revenue opportunities through cloud adoption.
|
||||
|
||||
The program addressed the extent of urban sprawl, which refers to the vast amount of infrastructure across data centers. A 2022 presentation to the Executive Leadership Team (ELT) highlighted nearly 20,000 assets across 14 data centers, costing millions in power and rent alone. *Micro Focus has the world's largest commercial footprint.* Despite a $2.5 billion annual revenue, Micro Focus's VMware footprint is larger than companies eight times its size, with hardware utilization under 40%. Migrating three products out of Bublikan led to decommissioning 575 physical servers, replaced by only 240 virtual servers in the cloud. 40% of applications in Redding were simply switched off upon exit, and Houston has 89 empty racks and 360 unused servers.
|
||||
|
||||
The benefits of moving to the cloud extend beyond cost savings, fostering innovation and increasing revenue. Cloud adoption enables product groups to enhance their products, improve disaster recovery, and explore new markets. A cloud-first policy provides a secure and resilient platform for innovation. Accomplishments in the past year include delivering a SAS landing zone, a landing zone in Tokyo, and managing the Dart divestiture. Live customer SAS workloads were migrated out of Redding into the cloud, and a SAS region was established in Oregon.
|
||||
|
||||
## Landing Zones and Terminology
|
||||
|
||||
The program clarified its terminology, particularly the concept of landing zones. Three types of landing zones have been delivered: labs, SAS, and corporate. Labs lack direct internet connectivity and customer data, while SAS zones support customer access and data. Corporate landing zones are a hybrid, hosting internal applications without customer data. The enterprise platform includes public cloud providers (AWS), SRE, CCOE, architecture groups, automation, security, and financial control.
|
||||
|
||||
## Financial Oversight and ROI
|
||||
|
||||
A consistent account tagging framework has been implemented across 609 AWS accounts to improve financial reporting. This framework allows for tracking spending and informing product groups about their consumption. The program is also working to refine figures related to return on investment (ROI), addressing commercial contracts and software components. Cloud adoption enables product groups to be more responsive to customers and open up new revenue opportunities in new regions.
|
||||
|
||||
## Key Objectives and Future Plans
|
||||
|
||||
Major objectives for the current fiscal year include:
|
||||
* Establishing landing zones in Canada and Australia (completed).
|
||||
* Standing up a corporate IT landing zone (completed).
|
||||
* Implementing an AWS account tagging framework (completed).
|
||||
* Delivering provisioning capabilities for demos and user training (Q2).
|
||||
* Improving the AWS account creation process (Q2 & Q3).
|
||||
* Closing the UAHD data center (Q2).
|
||||
* Migrating workloads out of the classic landing zone (Q2).
|
||||
* Establishing an Azure landing zone (Q3).
|
||||
* Moving more workloads onto the enterprise platform (Q4).
|
||||
|
||||
Currently, 55% of AWS costs are spent outside of landing zones, lacking automation, security, and financial control. The program is also focused on utilizing cloud-native services and tools to optimize costs and efficiency. *We're trying to give them the information so that they can understand how they are spending.*
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: CTP Topic 53 Why bother with Cloud
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Cloud
|
||||
- Strategy
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 53_ Why bother with Cloud_.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 53 Why bother with Cloud
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 53_ Why bother with Cloud_.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,17 +1,17 @@
|
||||
---
|
||||
title: "CTP Topic 57 Product backlog managing demand"
|
||||
title: CTP Topic 57 Product backlog managing demand
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Product-Backlog
|
||||
- Demand-Management
|
||||
- Agile
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 57_ Product backlog_ managing demand.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 57_ Product backlog_ managing demand.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 57 Product backlog managing demand
|
||||
@@ -26,7 +26,22 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## Product Backlog: Managing Demand
|
||||
|
||||
This session covers managing the product backlog, including why it's needed, how it's managed, and its effects. The backlog is a holding area for upcoming features, highlighting needs, benefits, and priorities. Managing it involves understanding the value, importance, effort, and complexity of each piece of work.
|
||||
|
||||
New requests should be submitted through SMACs to start the timer and ensure tracking. While email or chat are acceptable for initial contact, SMACs is the most reliable method. Demand is reviewed in twice-weekly meetings with Matthew Chapman, David Grant, Brendan, and others to assess understanding, value, and priority. A calculator with about 20 questions helps determine the simplicity, cost, and ambition of each request. *We need a way to make sure it's transparent and we're holding everything up to the light and looking everything for the same lens as we are.*
|
||||
|
||||
Once assessed, opportunities move into Octane as features with task lists. New teams undergo a prerequisite phase to align expectations and understand product needs. Planning involves mapping out upcoming work and important dates, typically six sprints ahead. Sprints allocate around 50% for new demand and 50% for support tickets and tech debt. Larger product groups like ADM and ITOM have fortnightly sessions to align plans and priorities. *It means that for ADM they can effectively plan all of the work that's going into their sprints with the engineers that are working solidly on their work.*
|
||||
|
||||
The prerequisite phase is crucial for product teams entering the transformation journey to the enterprise landing zone. It addresses questions about checklists, end goals, and stakeholder involvement. This phase gathers business and technical requirements, translating them into workable designs. Key components include introductory sessions, AWS account creation (reviewed with the PCG team), solution design and refinement, GitHub repository creation, and firewall tag definition. The effort estimate for the product team is about two hours, spread over one or two weeks.
|
||||
|
||||
After the prerequisite phase, SRE engineers build the account and hand it over, providing access details for the console and GitHub. A short demo of EC2 instances and other resources is given, along with CTP training videos. Two weeks of hyper care support is provided post-handover.
|
||||
|
||||
Existing product groups can request support via SMACs, email, or Teams. The support team assesses risk, complexity, and urgency. Defects are addressed in the current sprint, assigned to the original squad. A Teams channel is created for communication between the product group, SRE engineer, solution architect, and delivery manager. Change requests or enhancements are discussed with the solution architect to integrate them into the existing account.
|
||||
|
||||
Different support request types include adding VPCs, creating subnets, and managing roles/tags. Public subnets are generally restricted to production environments. The team provides guidance on using Atlantis or grant forms for self-service tasks. For urgent requests, the team assesses capacity and dependencies, potentially requiring additional approval from networking. Communication involves agreeing on timelines and providing updates through the Teams channel. Standard videos and wiki pages are shared for common requests.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: CTP Topic 57 Product backlog managing demand
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Product-Backlog
|
||||
- Demand-Management
|
||||
- Agile
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 57_ Product backlog_ managing demand.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 57 Product backlog managing demand
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 57_ Product backlog_ managing demand.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,17 +1,17 @@
|
||||
---
|
||||
title: "CTP Topic 6 AWS Workspaces Demo"
|
||||
title: CTP Topic 6 AWS Workspaces Demo
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- AWS
|
||||
- Workspaces
|
||||
- Demo
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 6_ AWS Workspaces Demo.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 6_ AWS Workspaces Demo.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 6 AWS Workspaces Demo
|
||||
@@ -26,7 +26,14 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## AWS Workspaces Demo
|
||||
|
||||
AWS Workspaces is a solution that provides users with a desktop environment, accessible via web browser or a downloaded client application. These remote desktops can be pre-configured with specific tooling or be vanilla Windows installations. The primary goal is to provide an AWS workspace with preconfigured tooling, enabling users to become productive quickly. *The hope is that within half an hour, 45 minutes of making a request for a workspace, you've run a Terra Grunt plan against a piece of infrastructure.*
|
||||
|
||||
The workspace includes tools like PF SSO, Terraform, TerraGrunt, Git, and VS Code, running on Windows Server 2016 due to Pulse UI compatibility issues with Amazon Linux. To request a workspace, users currently email Naga, who sets up an account. The process may integrate with Active Directory in the future. Users receive an email from Amazon Workspaces with setup details, including a registration code and username.
|
||||
|
||||
Once logged in, users can access the AWS console using Federation, GitHub Enterprise, and generate SSH keys. *As you can see, we can successfully access GitHub Enterprise as well.* A config file is created for GitHub authentication. The demonstration included cloning a repository, authenticating PFSSO, and running a TerraGrunt plan, which was achieved in approximately 21 minutes. The workspace stays active for an hour after use and can be customized with additional tooling as needed.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: CTP Topic 6 AWS Workspaces Demo
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- AWS
|
||||
- Workspaces
|
||||
- Demo
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 6_ AWS Workspaces Demo.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 6 AWS Workspaces Demo
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 6_ AWS Workspaces Demo.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,16 +1,16 @@
|
||||
---
|
||||
title: "CTP Topic 65 Tracing the value delivered in Cloud Transformation"
|
||||
title: CTP Topic 65 Tracing the value delivered in Cloud Transformation
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Value-Tracing
|
||||
- Cloud-Transformation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 65_ Tracing the value delivered in Cloud Transformation.mp4"
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 65_ Tracing the value delivered in Cloud Transformation.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# CTP Topic 65 Tracing the value delivered in Cloud Transformation
|
||||
@@ -25,7 +25,20 @@ status: raw
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
> ## CTP Value Delivery
|
||||
|
||||
The presentation covers processes, value, value streams, benefits quantification, and prioritization of CTP work using the weighted shortest job first method. It also touches on breaking down value into component features and outlines next steps for capturing and utilizing value.
|
||||
|
||||
A process is a methodical set of steps designed to achieve a specific output and outcome, driven by inputs like data, resources, time, money, and know-how. Processes transform inputs into outputs and outcomes, with actions triggered by events like month-end or sprint planning. Outcomes can be hard (time, cost, quality) or soft (improved health, wellbeing, security). *A simple way of thinking of an outcome is that there's usually going to be a desirable change in some important attribute or indicator.*
|
||||
|
||||
Value is defined as the monetary worth of something, determined by the customer, involving a fair return or equivalent goods. Lean identifies three types of activity within a process: value-adding, value-enabling, and waste. Value streams are sets of activities that deliver a product or service to a customer. Scaled Agile defines operational value streams (OVS) for customer-facing solutions and development value streams (DVS) for internal products.
|
||||
|
||||
To capture value, a holistic framework is needed, considering financial, productivity, quality, and experience benefits. The focus should be on revenue increase, cost reduction, risk position improvement, and serviceable obtainable market (SOM) size. For each demand, the demand manager captures these five things from the product team. Financial figures should be annualized. The size of the job is obtained from the delivery manager. *What we want to do is deliver the maximum value early back into the business for the least amount of effort.*
|
||||
|
||||
The weighted shortest job first method prioritizes work based on cost of delay (business value + time criticality + risk and opportunity) divided by size of job. This method helps sequence work for maximum economic benefit. To break down value at a feature level, options include attributing all value to a single feature, evenly apportioning value across features, or unevenly apportioning based on criteria like reach, impact, or effort.
|
||||
|
||||
Next steps involve demand managers capturing business benefits from product teams for new demands. Product teams should identify business benefits and provide estimates for business value, risk, opportunity, and time criticality. The goal is to sequence CTP work for maximum economic benefit, learning and fine-tuning the process as it's implemented.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: CTP Topic 65 Tracing the value delivered in Cloud Transformation
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: DevOps & SRE/10_OpenText-Series
|
||||
tags:
|
||||
- Value-Tracing
|
||||
- Cloud-Transformation
|
||||
- CTP
|
||||
date-added: 2026-04-14
|
||||
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 65_ Tracing the value delivered in Cloud Transformation.mp4
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# CTP Topic 65 Tracing the value delivered in Cloud Transformation
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 65_ Tracing the value delivered in Cloud Transformation.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -9,7 +9,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109_160114-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109 160114-Meeting Recording
|
||||
@@ -22,28 +22,24 @@ status: raw
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
## Business Analysis Techniques Learning Session
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
This learning session introduces business analysis, T-shaped skill sets, and learning resources. It focuses on three techniques for defining new work: BOSCARD (Background, Objectives, Scope, Constraints, Assumptions, Risks, Roles, Deliverables), the stakeholder wheel, and a method for gathering requirements that combines agile user stories with metadata.
|
||||
|
||||
---
|
||||
Business analysis aligns business needs with change solutions, considering IT and process changes, training, and role shifts. The business analysis process involves investigating the current situation, analyzing needs, identifying solutions, evaluating options, and defining requirements. Benefits include clarity and consistency. *Business analysis helps us work out what changes will be beneficial in our business architecture, including changes to IST systems and defining the requirements for those changes.*
|
||||
|
||||
## 关键概念
|
||||
T-shaped skills are valuable in agile squads, combining core expertise with a broad understanding of related skills. Business analysis skills bridge the gap between business problems and technical solutions. Resources for learning business analysis include the BCS and IIBA curriculums.
|
||||
|
||||
-
|
||||
### BOSCARD Technique
|
||||
|
||||
---
|
||||
BOSCARD defines complex new work by clarifying background, objectives, scope, constraints, assumptions, risks, roles, and deliverables. It helps avoid confusion about goals, timelines, and deliverables. *If you can get scope tied down early on and agreed, that's priceless.*
|
||||
|
||||
## 行动项
|
||||
### Stakeholder Wheel
|
||||
|
||||
-
|
||||
The stakeholder wheel identifies all stakeholders for a project, including customers, partners, regulators, employees, managers, owners, and competitors. Identifying stakeholders early prevents changes and uncovers risks. The wheel starts with the customer and moves clockwise. Stakeholder analysis can involve mapping stakeholders on a power/influence grid or creating a RACI (Responsible, Accountable, Consulted, Informed) chart.
|
||||
|
||||
---
|
||||
### Requirements Gathering
|
||||
|
||||
## 相关视频
|
||||
Combining user stories with metadata adds rigor to requirements capture. User stories capture the what, who, and why, but lack versioning, dependencies, and traceability. The Scaled Agile Framework (SAFe) includes features, capabilities, and non-functional requirements in addition to stories.
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
A detailed Excel sheet example captures requirements for a garage business, including user stories, versioning, dependencies, traceability, scheduling, acceptance criteria, and categorization (business, technical, functional). The INVEST acronym (Independent, Negotiable, Valuable, Estimable, Small, Testable) is used to check requirements. *Every requirement should be independent, meaning not duplicating something else, that's the I in invest, negotiable, so the business should state what they need, but be open to how it's implemented.*
|
||||
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109 160114-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- Business-Analysis
|
||||
- Techniques
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109_160114-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109 160114-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109_160114-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -10,7 +10,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- AWS end user compute services - 20240430_160120-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- AWS end user compute services - 20240430 160120-Meeting Recording
|
||||
@@ -23,28 +23,31 @@ status: raw
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
## AWS and User Compute Services
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
Christian O'Donough from AWS presented a learning session on AWS and user compute (EUC) services, covering virtual desktops, application streaming, and security considerations. The session aimed to provide an introduction to AWS EUC services, explain how to decide which service is best, and discuss security aspects of Amazon Workspaces and AppStream 2.0.
|
||||
|
||||
---
|
||||
The global pandemic accelerated the shift to remote and hybrid work models, requiring organizations to adapt quickly. Modern workforces include diverse users with varying needs, from task workers to knowledge workers, using both company-issued and personal devices. IT organizations face challenges in maintaining productivity, ensuring security, and managing costs in this hybrid environment. AWS EUC portfolio addresses these challenges with virtual desktops and application streaming services.
|
||||
|
||||
## 关键概念
|
||||
AWS offers several EUC options:
|
||||
* **Workspaces and AppStream 2.0:** All-inclusive virtual desktop services, differing in persistence. Workspaces are fully persistent, while AppStream 2.0 offers selective persistence.
|
||||
* **Workspace Core:** Provides access to Workspaces VDI infrastructure via API for third-party solutions like Horizon View or Citrix.
|
||||
* **Workspace Web:** A low-cost, secure web browser for internal websites and SaaS applications.
|
||||
* **AppStream 2.0:** A secure, reliable, and scalable solution for streaming applications from any location.
|
||||
* *AppStream 2.0 is a great low cost alternative for customers that don't require a fully persistent desktop.*
|
||||
|
||||
-
|
||||
The choice of service depends on the use case. Workspaces suit knowledge workers needing a full desktop, while AppStream is suitable for labs, training, and bastion hosts. Workspace Web is ideal for secure browsing. Fully persistent desktops (Workspaces) offer a one-to-one instance management, where application states and settings persist between sessions. Non-persistent desktops (AppStream) provide a fresh desktop at each logon, with options for creating application and storage connectors for some persistence.
|
||||
|
||||
---
|
||||
Operational excellence considerations include OS requirements. Workspaces supports Ubuntu and Windows, while AppStream is exploring other Linux flavors. AppStream instances are created from a base image, simplifying application management. Workspaces are deployed from bundles, allowing users to install applications with appropriate permissions. Monitoring is supported through CloudWatch events and third-party agents.
|
||||
|
||||
## 行动项
|
||||
Reliability considerations include autonomy, user configuration persistence (Workspaces), and network latency. WSP protocol is designed for high-latency networks. Disaster recovery strategies involve building out workspaces in another region or utilizing AppStream's auto-scaling capabilities.
|
||||
|
||||
-
|
||||
Performance-wise, all services support cut and paste with configurable policies. AppStream supports file uploads/downloads and offers a Windows client for native application support. Workspaces support smart cards, webcams, and various native clients. Hardware requirements vary, with AppStream offering more instance types.
|
||||
|
||||
---
|
||||
Cost optimization is achieved through concurrency of use (AppStream) and auto-stop features (Workspaces). A newer multi-tenant approach for AppStream allows multiple users per instance. Security measures include Active Directory integration, encryption, IAM profiles, and device authentication. *With so many remote workers organizations are struggling to protect endpoints, as well as their IP and data from bad actors.*
|
||||
|
||||
## 相关视频
|
||||
Workspaces maximize agility, productivity, security, and reliability while controlling costs. It suits hybrid workforces, BYOD users, developers, and compute-intensive workloads. The architecture involves a service VPC (managed by AWS) and a customer VPC, with two network interfaces for each workspace.
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
AppStream offers application streaming and virtual desktops with selective persistence. It allows centralized app management, flexible hardware types, and branding options for ISVs. Use cases include non-persistent desktops, secure access to corporate resources, online trials, and cloud migrations. Admins can control file movement to limit data transfer.
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
Maintaining a strong security posture involves secure streaming protocols, built-in data protection policies, device certificates, multi-factor authentication, and VPC interface endpoints. SAML-based authentication enhances security and streamlines user experience.
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- AWS end user compute services - 20240430 160120-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- AWS
|
||||
- End-User-Computing
|
||||
- Workspaces
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- AWS end user compute services - 20240430_160120-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- AWS end user compute services - 20240430 160120-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- AWS end user compute services - 20240430_160120-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -11,7 +11,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723_160210-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723 160210-Meeting Recording
|
||||
@@ -24,28 +24,12 @@ status: raw
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
The learning session focuses on evolving disaster recovery (DR) mechanisms to recovery assurance, presented by Jim Rose. The primary objectives include understanding the current state of DR for OpenText solutions and the trend toward site reliability engineering (SRE) and observability engineering to enhance recovery assurance.
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
Jim Rose discusses the CrowdStrike incident, where a software vulnerability caused widespread system outages, emphasizing the importance of robust DR strategies. *CrowdStrike was not us, but we have had some disruptions.* He highlights past incidents like the 2003 Power Grid outage and the 2017 WannaCry ransomware attack to illustrate potential disaster impacts. OpenText has experienced incidents, driving the need for improved end-to-end system management.
|
||||
|
||||
---
|
||||
Key DR terms include Recovery Time Objective (RTO), the time to restore services after an event, and Recovery Point Objective (RPO), the amount of data that might be lost. OpenText's RTO and RPO vary from minutes to days based on customer contracts. Testing is often reactive, manual, and customer-scheduled, involving many teams and significant effort. *Every person who is a SME on some part of this has to be involved in developing a plan.* The company aims to shift to a more proactive stance for better scalability.
|
||||
|
||||
## 关键概念
|
||||
Several factors are driving change, including the increasing use of AWS, GCP, and Azure for hosting solutions. Testing in hyperscalers has limitations, such as focusing on zone failures rather than other potential issues. Hybrid solutions, where only part of the service can be failed over, pose additional challenges. The current model lacks a consistent approach across the organization, especially for systems that have not been tested.
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
The discussion covers four key areas: design, software, build, and environments. Recoverability should be a design principle, with mechanisms for data and environment recovery conceived early. Software should provide telemetry to understand system health continuously, with self-healing capabilities. The build process should include a customer zero environment for validating new products and releases. Environments should leverage observability engineering and SRE to improve resilience and capacity. Automation is seen as a future opportunity to reduce manual effort and time delays in DR processes.
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723 160210-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- OpenText
|
||||
- DR
|
||||
- Recovery
|
||||
- BCP
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723_160210-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723 160210-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - Evolving from DR to Recovery Assurance - 20240723_160210-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -11,7 +11,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab migration - 20240625_170052-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab migration - 20240625 170052-Meeting Recording
|
||||
@@ -24,28 +24,21 @@ status: raw
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
## GitHub Enterprise to GitLab Migration
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
The session covers the migration of source code from GitHub Enterprise to GitLab, driven by the company's decision to standardize on GitLab as the golden standard for source control. The GitHub license is expiring at the end of December, with no intention to renew, while the GitLab license covers up to 8,500 users. The migration approach is self-serve, with teams defining their needs and transforming their pipelines, with assistance from the Build Hub team when needed.
|
||||
|
||||
---
|
||||
Key points include:
|
||||
|
||||
## 关键概念
|
||||
* Project Thor aims to integrate micro-focus and open-text tooling, with GitLab as the centralized system for source control.
|
||||
* The Build Hub team manages central tools like GitLab and provides support for software delivery pipelines.
|
||||
* *Each team will define what they have in GitHub today, how they're using it, and they will plan to move it and change their pipelines.*
|
||||
* Definition of done includes code migration, pipeline transformation, and updating PHT (Product Hub platform).
|
||||
* Permissions for source repos in GitLab will be controlled by PHT, allowing self-service access management.
|
||||
* Personal repos are allowed in GitLab but should not contain product source code and will not be mapped in PHT.
|
||||
|
||||
-
|
||||
Migration approaches include mirroring (synchronizing GitHub repo to GitLab) and shift and lift (copying code to GitLab and transforming pipelines). Tracking will be done via PHT, with regular updates to dev managers and build advocates. Planning guidelines include inventorying GitHub assets, identifying pipelines, and understanding network connectivity.
|
||||
|
||||
---
|
||||
A significant challenge is the service account standard, requiring service accounts to be linked to a person, with expiring passwords. Other standards include repo naming conventions and segregation of duties. Network connectivity challenges were addressed by creating a GitLab proxy in Brook Park, accessible through SD1. *The current solution that is working and is efficient and is actually reporting to scale.* Commercial instances connecting to GitLab may require an exception from the GIS team.
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
Implementation steps involve installing GitLab plugins, getting early access to GitLab, mapping repos to PHT, setting up service accounts, and updating pipelines. The session also touched on the importance of testing network connectivity before planning the migration.
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab migration - 20240625 170052-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- GitHub
|
||||
- GitLab
|
||||
- Migration
|
||||
- OpenText
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab migration - 20240625_170052-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab migration - 20240625 170052-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - GitHub Enterprise to GitLab migration - 20240625_170052-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -10,7 +10,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Product Hub (PHT) Overview and Q&A - 20240806_170251-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText)- Product Hub (PHT) Overview and Q&A - 20240806 170251-Meeting Recording
|
||||
@@ -23,28 +23,12 @@ status: raw
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
## Product Hub (PhD) Overview and Q&A
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
The session provides an overview of the Product Hub (PhD), also known as the Product Hierarchy Tracker. PhD gathers product-related information, driven by product or development managers. It stores official products and their divisions, including business units and lines of business, differing from master products in the official product naming registry.
|
||||
|
||||
---
|
||||
A product is a software distribution with its own CI/CD pipeline or release cycle. *A product may also be part of another parent product, but if that particular product has its own cycle, like its own CACD pipeline or its own distribution, then we may treat that particular component or module as a product in PhD.* Each product consists of metadata like attributes, source reports, artifact reports, and user information, integrated into external applications like PSMQ, P2M, ITLS, and Backstage. Components are libraries without CI/CD pipelines and may or may not be part of a product. If a component needs ITLS review or scanning, it should be created as a product.
|
||||
|
||||
## 关键概念
|
||||
PhD has hierarchy levels: business units, lines of business, and products. Business units have engineering and PM leaders, while lines of business have owners and PM leaders. Products are managed by product and development managers and relate to a master product. Requesting a new product is a self-serve process; after submission, it goes to LOB approval, where the line of business owner reviews it. Active products have regular releases; maintenance mode indicates only hotfixes or bug fixes, and inactive means no releases. Product information includes business unit, line of business, product name, product manager, development manager, and status. Attributes store metadata like alternate names, build advocates, and release gate mechanisms (e.g., P2M). Source and artifact repos are mapped for source control permissions, managed through PhD. Related products and components specify relationships, with source repo permissions shared to child products with read-only access.
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
PhD integrates with applications like Jira, Value Edge, PSMQ, and OSS. Source repo creation in GitLab takes 24 hours to reflect in PhD, and empty groups/repositories cannot be searched. Artifact repo permissions are enabled for new structures. For product name/status changes, contact erphd@opentext.com; for technical questions, contact aangetoolsupport@opentext.com. The demo covered filtering products, hierarchy levels (business units, lines of business, master products, products), and creating new products. *Requesting for a new product is a self-serve process.* The process includes filling in BU, LOB, product name, and manager information. Attributes like release gate mechanism are mandatory. Source repos and artifact repos can be mapped, with source repo ownership taken by the product. Dependencies can be specified, and product teams/guests can be mapped for access control. Teams can be created with engineering (right access) or moderator (maintainer access) types. Components are created by role managers and do not have CI/CD pipelines or approval processes.
|
||||
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions (OpenText)- Product Hub (PHT) Overview and Q&A - 20240806 170251-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- Product-Hub
|
||||
- PHT
|
||||
- OpenText
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Product Hub (PHT) Overview and Q&A - 20240806_170251-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText)- Product Hub (PHT) Overview and Q&A - 20240806 170251-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Product Hub (PHT) Overview and Q&A - 20240806_170251-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -1,48 +0,0 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions (OpenText) - Product Hub (PHT) Overview and Q&A important information - 20240806 170251"
|
||||
type: cloud-learning
|
||||
source-type: pptx
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- uncategorized
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - Product Hub (PHT) Overview and Q&A important information - 20240806_170251.pptx"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText) - Product Hub (PHT) Overview and Q&A important information - 20240806 170251
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText) - Product Hub (PHT) Overview and Q&A important information - 20240806_170251.pptx`
|
||||
|
||||
**Type:** PPTX | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
@@ -9,7 +9,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429_170111-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429 170111-Meeting Recording
|
||||
@@ -22,28 +22,33 @@ status: raw
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
## Open Text Tagging Standard V2
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
Martin Rosler presented the Open Text Tagging Standard V2, emphasizing the value of standardized tags for cloud resources, container images, and Kubernetes objects. The session aimed to increase awareness of the tagging standard and prepare attendees to apply compliant tags.
|
||||
|
||||
---
|
||||
The three main drivers for the standard are:
|
||||
* Saving money through cloud cost optimization.
|
||||
* Reducing risk by easily identifying technical contacts for resources.
|
||||
* Improving efficiency via automation using tags as filters and selectors.
|
||||
|
||||
## 关键概念
|
||||
*It is about taking resources and you will learn more in the presentation about what kinds of object and what exactly and so on.* The standard helps with cost allocation, improved security and compliance, cloud service delivery, and resource organization. Currently, Open Text manages around 3,500 cloud accounts across 48 landing zone types, highlighting the need for consistency. The tagging standard, initiated in 2023 by the Phenops team, now includes guidelines for Kubernetes objects and container images.
|
||||
|
||||
-
|
||||
The scope of the tagging standard includes cloud accounts, cloud resources (compute, storage, network), Kubernetes objects (namespaces, pods, deployments, services, config maps), and container images. The standard is complementary to existing tagging practices, encouraging the adoption of standard tags alongside proprietary ones, with a gradual deprecation of the latter.
|
||||
|
||||
---
|
||||
Key concepts include:
|
||||
* Using a specific lowercase syntax with underscores for cloud resources.
|
||||
* Prefixing tags to ensure unambiguous semantics (e.g., OT\_ for cloud tags, app.opentext.com for Kubernetes labels, com.opentext.image for container image tags).
|
||||
* Defining the terms customer and tenant clearly, where customer refers to the company being hosted for, and tenant represents the contractual agreement or software instance.
|
||||
* Distinguishing between environment (Open Text's perspective) and service instance (customer's perspective).
|
||||
|
||||
## 行动项
|
||||
The Wiki page provides details on proposed tags, including definitions, applicability, and permitted values. Examples of tags for cloud accounts and resources include OT business unit (OTPU) and OT technical contact. Kubernetes objects have similar tags like product, customer, and environment, along with Kubernetes-specific tags like part of, name, and version. Container images include tags for product, title, description, and vendor, with special labels for base images and their versions.
|
||||
|
||||
-
|
||||
*Texts are key value pairs that typically have a tag key and an optionally a key value, which you can attach to cloud resources, cloud accounts, container images, Kubernetes objects and other things.*
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
Best practices for applying tags include:
|
||||
* Using infrastructure as code (e.g., Terraform) to automate tag creation and maintenance.
|
||||
* Creating checks and reports to detect missing tags.
|
||||
* Avoiding storing sensitive data in tags.
|
||||
* Being cautious about mandating tags for easily derivable information (e.g., region, account ID).
|
||||
* Handling indirect creation of resources (e.g., Kubernetes creating load balancers) using annotations.
|
||||
* Being careful with tags that frequently change to minimize maintenance overhead.
|
||||
|
||||
@@ -1,23 +1,22 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429 170111-Presentation"
|
||||
title: "Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429 170111-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: pdf
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- OpenText
|
||||
- Tagging-Standard
|
||||
- Presentation
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429_170111-Presentation.pdf"
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429_170111-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429 170111-Presentation
|
||||
# Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429 170111-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429_170111-Presentation.pdf`
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- OpenText Tagging Standard v2 - 20250429_170111-Meeting Recording.mp4`
|
||||
|
||||
**Type:** PDF | **Category:** 10_OpenText-Series
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
@@ -10,7 +10,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210_160056-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210 160056-Meeting Recording
|
||||
@@ -23,28 +23,10 @@ status: raw
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
## Platform and Flows: A Summary
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
Arnold Dacan presented an overview of the platform and its data flows, including updates on the foreign store platform system layout using on source build related data flows, tool to tool data flow, source code data flow, and artifacts data flow. The session covered Project Thor, supply chain security, and the current tooling landscape. The presentation emphasized the importance of standardization, consolidation, and automation to improve developer experience and security.
|
||||
|
||||
---
|
||||
Key discussion points included the five pillars of Project Thor: agile and right cycle management, product and release governance, the developer portal (backstage), security and vice as governance, and build hub. The goal is to standardize tooling across the platform, integrating governance models and promoting tools like GitLab, Artifactory, and various internal tools. *The main ingredient in the supply chain is our source code, our IP that is intended to live in GitLab.* The presentation highlighted the current state of the source and build supply chain, emphasizing the flow of source code from GitLab through the manufacturing process (build farms) to Artifactory and ultimately to customer environments.
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
The presentation detailed the geographical distribution of engineering resources, highlighting the distinction between the legacy Micro Focus network and the OpenText network. The main presence for tooling, source, and build is in Brook Park, with expansions to Sacramento for disaster recovery and business continuity. Data flows for source code, artifacts, and tool-to-tool connections were explained, including the role of GitLab proxies, GitLab geo for business continuity, and code signing processes. *We are trying to standardize in get lab, anti factory, PMS and UCMDB are back end services with started to grow and will grow further for supply chain security.* The session concluded with a look at the next phase of Project Thor, focusing on saving engineers time, enhancing supply chain security, and creating a seamless, integrated platform.
|
||||
|
||||
@@ -1,24 +1,23 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210 160056-Presentation"
|
||||
title: "Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210 160056-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: pdf
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- Thor
|
||||
- Platform
|
||||
- OpenText
|
||||
- Presentation
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210_160056-Presentation.pdf"
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210_160056-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210 160056-Presentation
|
||||
# Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210 160056-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210_160056-Presentation.pdf`
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions (OpenText)- Thor Platform & Flows - 20241210_160056-Meeting Recording.mp4`
|
||||
|
||||
**Type:** PDF | **Category:** 10_OpenText-Series
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
@@ -12,7 +12,7 @@ tags:
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Tagging Standards for all hyperscalers - 20240123_160135-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
status: summarized (Gemini 摘要)
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Tagging Standards for all hyperscalers - 20240123 160135-Meeting Recording
|
||||
@@ -21,32 +21,19 @@ status: raw
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
## Open Text Tagging Standards for Hyperscalers
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
The aim is to establish a tagging standard across all of Open Text to optimize hyperscaler costs (AWS, GCP, and Azure), which are projected to be around $500 million over the next three years. Reducing cloud waste from an industry average of 30% to 15% could save approximately $25 million annually and improve sustainability. A formal finance organization led by Tom Bice is focused on providing reporting across the business, requiring detailed annotation of resources and accounts through tagging.
|
||||
|
||||
---
|
||||
Tagging is essential for cost allocation, optimization, resource responsibility, and classifying resources (production, labs, customer data). The tagging pipeline involves enabling specific tags for billing in the billing console, which then includes the value of those tags in the cost and usage report (CUR) for reporting via HCMX, Phenops, QuickSight, and Power BI. Consistency in tagging is crucial to avoid ad hoc tag mapping, which is difficult to manage and doesn't compensate for untagged resources. *If we can agree the tags that need to go here, we don't have to do this and we can get out the analysis results.*
|
||||
|
||||
## 关键概念
|
||||
The goals of the Open Text tagging standard include supporting key business reporting, applying to all Open Text accounts across all hyperscalers, and being practical for quick implementation. The standard uses the terms tag and account (label and project in GCP). Due to the varying implementations of tagging across hyperscalers, the standard adopts the lowest common denominator, which is GCP's restrictive character set (lowercase, digits, hyphens, and underscores). Many concepts apply at both the account and resource level, using the same tag name and value set. Tags are prefixed with OT_ to differentiate them, with exceptions for existing tags like environment, BU, and cost center, and special cases like name in AWS.
|
||||
|
||||
-
|
||||
The standard was developed over three months with input from a working group and other contributors and was approved on October 3rd of last year. Tags that are not required are those easily obtained directly for FINOPs or UCMDB collection, such as account, region, hyperscaler, and resource name. Proposed tags include business unit (BU), OT technical contact, cost center, customer, tenant, environment, OT master product, custom fields, platform, cost type, and customer data. The standard is currently on Confluence, and access can be provided if needed.
|
||||
|
||||
---
|
||||
Implementation involves piloting with product teams to refine the standard and ensure it delivers value in FinOps. Tagging is currently owned by FinOps, with coordination to ensure results and address any issues. A list of product short codes and business units will be maintained in Confluence, backed by Excel, until a proper product hub implementation is available. Future plans include implementing a tagging dictionary and potentially forming a committee to govern the standard. A KPI for tagging, such as 99% of taggable resources being tagged, may be enforced via SCPs or tagging policies.
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
There's a history of tagging in Micro Focus, with tags specified by the network team for the checkpoint firewall and tags related to the CCRE guardrails. The checkpoint firewall currently references only account number and role, while the CCRE guardrails have a more extensive list. Rationalizing tagging policies and SCPs is ongoing to simplify administration and enforcement. Setting tags is typically done using Terraform, with modules like AWS instance module having a tags parameter. Default tags can be included in the provider definition for easy application across resources. *Typically what you do is almost every module that you've got inside Terraform, so like the AWS instance module there, there's a tags parameter that you could use.*
|
||||
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: "Public Cloud Learning Sessions- Tagging Standards for all hyperscalers - 20240123 160135-Meeting Recording"
|
||||
type: cloud-learning
|
||||
source-type: video
|
||||
category: "DevOps & SRE/10_OpenText-Series"
|
||||
tags:
|
||||
- Tagging-Standard
|
||||
- AWS
|
||||
- Azure
|
||||
- GCP
|
||||
- FinOps
|
||||
date-added: 2026-04-14
|
||||
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Tagging Standards for all hyperscalers - 20240123_160135-Meeting Recording.mp4"
|
||||
audio-source: ""
|
||||
status: raw
|
||||
---
|
||||
|
||||
# Public Cloud Learning Sessions- Tagging Standards for all hyperscalers - 20240123 160135-Meeting Recording
|
||||
|
||||
**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Tagging Standards for all hyperscalers - 20240123_160135-Meeting Recording.mp4`
|
||||
|
||||
**Type:** VIDEO | **Category:** 10_OpenText-Series
|
||||
|
||||
**Status:** 🟡 Awaiting Whisper transcription → Summary
|
||||
|
||||
---
|
||||
|
||||
## 摘要
|
||||
|
||||
> 待转录后由 LLM 生成
|
||||
|
||||
---
|
||||
|
||||
## 关键概念
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 行动项
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## 相关视频
|
||||
|
||||
> 配对视频笔记链接（生成后填入）
|
||||
|
||||
---
|
||||
|
||||
*最后更新: 2026-04-14*
|
||||
Reference in New Issue
Block a user