Batch: enforce full 7-field frontmatter on all 360 notes (obsidian_frontmatter.py v3)
This commit is contained in:
@@ -1,9 +1,16 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
kanban-plugin: board
|
||||
---
|
||||
|
||||
|
||||
|
||||
## Backlog
|
||||
|
||||
- [ ] 🔼 Email to Nina about Achmea Pen Testing on EU3, WAF result reported
|
||||
|
||||
@@ -1,9 +1,16 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
kanban-plugin: board
|
||||
---
|
||||
|
||||
|
||||
|
||||
## TikTok Shop Tasks
|
||||
|
||||
- [ ] ⏫ 等营业执照下来注册TikTok Shop
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
## 1. Review Upgrade Procedures Document with R&D team
|
||||
## 2. Follow the Upgrade Procedures to perform Dev Farm upgrade validation
|
||||
## 3. Send Notification to ESM Cloud Farm Customer about upcoming maintenance window
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
Control Tower Link: https://backoffice.saas.microfocus.com/home/bl/desktop.html?TENANTID=1#/customers
|
||||
|
||||
- Request Access to Control Tower
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
Wiki Page:
|
||||
https://confluence.opentext.com/display/ICSD/Request+Unplanned+Change+in+Cloud+Production+Environment+Process
|
||||
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
## Review R&D Major Release Plan & Patch Plan
|
||||
- ESM RTE: Mihaela Claudia Chis <mchis@opentext.com>
|
||||
- PI Planning Readout Slides
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
## ESM Cloud
|
||||
- ESM Farm Information: https://confluence.opentext.com/display/ICSD/ITOM+ESM+Cloud+Farm+Information
|
||||
- ESM Capability Introduction
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
- Major Incident Definition: https://confluence.opentext.com/display/ICSD/Major+Incident+Definition
|
||||
- Major Incident Management & Best Practice:
|
||||
- Identification and Detection
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
BI report:
|
||||
|
||||
https://app.powerbi.com/groups/fac06a69-6340-4715-b8fe-4bdc0ca9af14/reports/1f4989a9-0127-4c6d-9375-f9dd9bda5d84/ReportSection?experience=power-bi
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
PCS: https://pcs.saas.microfocus.com/homepage?AUTH=SAML
|
||||
|
||||
ITOM Cloud Ops Assignment Group:
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
## Role and Responsibility
|
||||
#### Strategic Responsibilities
|
||||
- Own the reliability and performance of multiple SaaS Application Services. (APM, BPM, OpsB, NOM, ESM, DCA, SBM, ESM FedRAMP)
|
||||
|
||||
@@ -1,7 +1,13 @@
|
||||
---
|
||||
title: AWS → GCP
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# AWS → GCP
|
||||
|
||||
To migrate your enterprise-level SaaS application from AWS to Google Cloud, you’ll need to find equivalent Google Cloud services for the AWS services you currently use, while ensuring your architecture remains compatible. Here's a service-by-service breakdown for smooth development:
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
#### Major Incident Management Process
|
||||
|
||||
Certainly! Designing a comprehensive Major Incident Management process is crucial for maintaining the reliability and availability of enterprise SaaS applications. Below is a detailed outline of the major incident management process, including procedures for handling service outages:
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
## Introduction
|
||||
The main purpose of this document is to help non-Cloud Ops team members better understand the various services and tools currently provided for Cloud Application troubleshooting, so that they can be used flexibly in different scenarios and reduce dependence on Cloud Ops engineers.
|
||||
Our goal is also very clear. We hope to provide a more efficient DevOps ecosystem to provide better services to our customers.
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
## Product Service
|
||||
### ESM Product
|
||||
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
## Role and Responsibility
|
||||
#### Strategic Responsibilities
|
||||
- Own the reliability and performance of multiple SaaS Application Services. (APM, BPM, OpsB, NOM, ESM, DCA, SBM, ESM FedRAMP)
|
||||
|
||||
@@ -1,11 +1,15 @@
|
||||
---
|
||||
title: Cloud Service “Bilities”
|
||||
source:
|
||||
author: shenwei
|
||||
published: 2025-03-01
|
||||
created: 2025-03-01
|
||||
description:
|
||||
tags: []
|
||||
link:
|
||||
---
|
||||
|
||||
|
||||
# Cloud Service “Bilities”
|
||||
|
||||
**The "bilities"**
|
||||
|
||||
@@ -1,7 +1,13 @@
|
||||
---
|
||||
title: ITOM Cloud Service Review Meeting
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# ITOM Cloud Service Review Meeting
|
||||
|
||||
### ESM
|
||||
|
||||
@@ -1,7 +1,14 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
### Mar 19
|
||||
- ESM 25.2 upgrade validation plan - Ting Ye
|
||||
- ESM Change Management Process Update - Ting Ye
|
||||
|
||||
@@ -8,6 +8,15 @@ title: **ITOM ESM Cloud Service Monthly Report - Feb 2025**
|
||||
author: shenwei
|
||||
tags: [Cloud, Customer, Product]
|
||||
---
|
||||
---
|
||||
title: **ITOM ESM Cloud Service Monthly Report - Feb 2025**
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [Cloud, Customer, Product]
|
||||
---
|
||||
|
||||
# Table of Content:
|
||||
- [[#Product Cloud Service|Product Cloud Service]]
|
||||
|
||||
@@ -1,11 +1,14 @@
|
||||
---
|
||||
title: **ITOM ESM Cloud Service Monthly Report - Jan 2025**
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created: 2025-03-02
|
||||
description: This report contains the main work of the ESM Cloud Service team and shows the load of the team's work in the form of data, and describes some issues and risks for continuous improvement.
|
||||
tags: [Cloud, Customer, Product]
|
||||
---
|
||||
|
||||
|
||||
# **ITOM ESM Cloud Service Monthly Report - Jan 2025**
|
||||
|
||||
**2025/1/1 ~ 2025/1/31**
|
||||
|
||||
@@ -1,8 +1,15 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
|
||||
Entitlement
|
||||
|
||||
- Create new company
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
|
||||
|
||||
I'm a senior manager responsible for SaaS operations and maintenance for cloud products in a global enterprise software company. I manage a global cloud operations team of 20+ people. The team is a global team covering different time zones. Our team is also responsible for interfacing with the product RnD team to understand requirements and communicate with them. I am designing myself and my team's goals from the below perspective: Leadership Activities, service delivery quality, Process Standardization, Operational Excellence, and Satisfy customers. could you please prepare a draft for me with efforts detail, and measurable KPIs for the above areas.
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
## **1. Objective**
|
||||
|
||||
Ensure business continuity and data protection by implementing an effective DR strategy for the customer, leveraging EFS replication, RDS PITR, and different failover methods.
|
||||
|
||||
Reference in New Issue
Block a user