Update by hanx@lhws312.ihep.ac.cn at 2026-01-20 19:52:59

Author: hanx-hep

public/images/legacyAdaptor.png

@@ -213,7 +213,6 @@ title: Summary of Performance Issues
 
 * **Queue Management**: Job scheduling inefficiencies under peak loads
 
-
 ---
 layout: top-title-two-cols
 color: gray-light
@@ -224,54 +223,7 @@ columns: is-7
 
 :: title ::
 
-# Memory Peak for Sandbox Store Service
-
-:: left ::
-
-Memory usage of all DIRAC services are monitored
-
-### Memory Overflow
-
-Still investigating
-
-but the DIRAC system is too complex, and the runit process management is outdated.
-
-### Quick Fix
-
-- A daemon process restarts services when services overload.
-- Weekly restart of critical services
-
-
-:: right ::
-
-<div style="width: 100%; height: 20vh; overflow: hidden;">
-  <iframe
-    src="https://dci-grafana.ihep.ac.cn/d-solo/9s0Ru8wVk/service-monitoring?var-bin=30m&orgId=1&from=1767977729000&to=1768030252000&timezone=browser&var-ServiceName=WorkloadManagement_SandboxStore&var-HostName=prod-dirac.ihep.ac.cn&theme=light&panelId=3&__feature.dashboardSceneSolo"
-    style="
-      width: 200%;
-      height: 40vh;
-      transform: scale(0.5);
-      transform-origin: 0 0;
-      border: 0;
-    "
-  ></iframe>
-</div>
-
-Service was restarted manually during the campaign to clear memory usage.
-
-And Sandbox recovered after the restart.
-
----
-layout: top-title-two-cols
-color: gray-light
-align: c-l-l
-title: Performance Screenshots and Analysis
-columns: is-7
----
-
-:: title ::
-
-# High disk I/O for prod-dirac.ihep.ac.cn
+# High disk I/O for DIRAC main server
 
 :: left ::
 
@@ -282,7 +234,7 @@ Machine metrics for all DCI servers are monitored.
 - Disk I/O usage reaches 90% for prod-dirac.ihep.ac.cn
 <!-- - Disk I/O bottlenecks during mass data transfers -->
 - Read operations queued during high I/O periods
-- Sandbox not responding
+<!-- - Sandbox not responding -->
 
 ### Quick Fix
 
@@ -319,6 +271,54 @@ Machine metrics for all DCI servers are monitored.
 ></iframe>
 </div>
 
+---
+layout: top-title-two-cols
+color: gray-light
+align: c-l-l
+title: Performance Screenshots and Analysis
+columns: is-7
+---
+
+:: title ::
+
+# Memory Peak for Sandbox Store Service
+
+:: left ::
+
+Memory usage of all DIRAC services are monitored
+
+### Memory Overflow
+
+Still investigating
+
+but the DIRAC system is too complex, and the runit process management is outdated.
+
+### Quick Fix
+
+- A daemon process restarts services when services overload.
+- Weekly restart of critical services
+
+
+:: right ::
+
+<div style="width: 100%; height: 20vh; overflow: hidden;">
+  <iframe
+    src="https://dci-grafana.ihep.ac.cn/d-solo/9s0Ru8wVk/service-monitoring?var-bin=30m&orgId=1&from=1767977729000&to=1768030252000&timezone=browser&var-ServiceName=WorkloadManagement_SandboxStore&var-HostName=prod-dirac.ihep.ac.cn&theme=light&panelId=3&__feature.dashboardSceneSolo"
+    style="
+      width: 200%;
+      height: 40vh;
+      transform: scale(0.5);
+      transform-origin: 0 0;
+      border: 0;
+    "
+  ></iframe>
+</div>
+
+Service was restarted manually during the campaign to clear memory usage.
+
+And Sandbox recovered after the restart.
+
+
 ---
 layout: top-title
 color: gray-light
@@ -371,9 +371,9 @@ columns: is-7
 
 :: content ::
 
-- Logs for all DIRAC services are monitored
+<!-- - Logs for all DIRAC services are monitored -->
 
-     High load for Configuration Service / Sandbox Store
+-  High load for Configuration Service / Sandbox Store
 
 ![Config service](/public/images/cs_log.jpg)
 
@@ -383,6 +383,8 @@ columns: is-7
 
 - Added a load-balanced Configuration Service
 
+- Adjusted the scheduling policy to reduce the number of jobs that end at the same time
+
 
 <!-- --- -->
 <!-- layout: top-title-two-cols -->
@@ -448,7 +450,7 @@ columns: is-6
 
 ### Long-term Solutions
 
-**DiracX, "the neXt Dirac incarnation"**
+**Service Scaling**
 - Horizontal scaling of Dirac services
 - Database sharding and replication strategies
 
@@ -457,6 +459,7 @@ columns: is-6
 - Network optimization between key sites
 
 **Architecture Evolution**
+- DiracX, "the neXt Dirac incarnation"**
 - Migration to DiracX services
 - Containerization of critical components
 
@@ -495,25 +498,22 @@ timeline
           2006-2007 : DIRAC3<br> Full rewriting, development of the DISET protocol -- still in use today!
                     : the current DIRAC framework is still based on this work
         section Open sourced, wider adoption
-          2008 : Large-ish reshuffling to become multi-VO
+          2008 - 2010s : Large-ish reshuffling to become multi-VO
                : LHCbDIRAC extension separated from core DIRAC code
                : CLIC community adopts DIRAC
                : France-Grilles is the first multi-VO DIRAC installation
                : 2010s - Belle2, BES3, CTA adopt DIRAC
-          2021-2022 : Python3 full support
-                    : DIRAC v8.0
-          2023-2025: First DiracX demo (during)
-                   : LHCb deploys in production alpha versions of DIRAC (v9.0.0aX) and DiracX (v0.0.1aX)
-                   : All existing DiracX components are tested and extended.
-                   : Several scalability and performance issues were addressed
+          2020s    : Python3 full support
+                   : DIRAC v8.0
+                   : First DiracX demo (during)
         section DIRAC and DiracX coexisting
-          Q4 2025 : Release of DIRAC v9.0 and DiracX 0.0.1
-                  : JobStateUpdate service migrated and tested
-                  : Possible adoption by non-LHCb DIRAC users
-        section DIRAC and DiracX coexisting (plan)
-            Q1 2026 : Release DiracX 0.1.0
+            2025 - 2026 
+                   : LHCb deploys DIRAC and DiracX
+                    : Release of DIRAC v9.0 and DiracX 0.0.1
+                    : JobStateUpdate service migrated and tested
+                    : Release DiracX 0.1.0
                     : DiracX introduces a task management system
-            Q3 2026 : Release DIRAC v9.1 and 0.1.X (or 0.2.0)
+            Plan : Release DIRAC v9.1 and 0.1.X (or 0.2.0)
                     : First DiracX-only service.
                     : Adoption of new Pilot security mechanism
                     : First DiracX replacements for DIRAC agents or executors using DiracX tasks
@@ -522,63 +522,122 @@ timeline
 
 
 ---
-layout: section
-color: blue-light
+layout: top-title
+color: gray-light
+align: c
+title: System Evolution Plan
 ---
 
-# Future Upgrade Plans
+:: title ::
+# DIRAC Upgrade & Migration Steps
+
+:: content ::
+
+# Key Technical Features
+
+<ul class="text-base leading-7">
+  <li>Containerized deployment to ensure standardized and portable runtime environments</li>
+  <li><b>Kubernetes orchestration</b> to support automated operations and elastic scaling</li>
+  <li><b>MySQL</b> + <b>OpenSearch</b> to improve log/metadata search efficiency</li>
+  <li><b>S3 object storage</b> to optimize job sandbox management and data access performance</li>
+  <li>A modern authentication system based on <b>OAuth2/OpenID</b> to enhance security</li>
+</ul>
+
+
+<div class="flex justify-between text-xs text-gray-500 mt-2 px-2">
+  <span>Start</span>
+  <span>Complete</span>
+</div>
+
+<div class="flex items-center gap-4 text-center">
+  <div class="rounded-xl border px-4 py-3 w-[220px] bg-blue-100">
+    <div class="font-semibold text-sm">Database Upgrade</div>
+    <div class="text-xs text-gray-700 mt-1">Add VO fields, rename tables, etc.</div>
+  </div>
+
+  <div class="text-xl font-bold">→</div>
+
+  <div class="rounded-xl border px-4 py-3 w-[220px] bg-green-100">
+    <div class="font-semibold text-sm">Containerized Deployment</div>
+    <div class="text-xs text-gray-700 mt-1">Host → Container</div>
+  </div>
+
+  <div class="text-xl font-bold">→</div>
+
+  <div class="rounded-xl border px-4 py-3 w-[220px] bg-orange-100">
+    <div class="font-semibold text-sm">Dual-Stack Parallel Operation</div>
+    <div class="text-xs text-gray-700 mt-1">DIRAC 9 + DiracX</div>
+  </div>
+
+  <div class="text-xl font-bold">→</div>
+
+  <div class="rounded-xl border px-4 py-3 w-[220px] bg-red-100">
+    <div class="font-semibold text-sm">Extension Module Adaptation</div>
+    <div class="text-xs text-gray-700 mt-1">IHEPDIRAC migration</div>
+  </div>
+
+  <div class="text-xl font-bold">→</div>
+
+  <div class="rounded-xl border px-4 py-3 w-[220px] bg-teal-100">
+    <div class="font-semibold text-sm">DiracX Only</div>
+    <div class="text-xs text-gray-700 mt-1">Migration of key subsystems</div>
+  </div>
+</div>
+
+
 
 ---
 layout: top-title
 color: gray-light
 align: c
-title: System Upgrade Roadmap
+title: Migration
 ---
 
 :: title ::
 
-# System Upgrade Roadmap
+### Migration to DiracX
+
 
 :: content ::
 
-```mermaid
-%%{init: {'theme': 'base', 'timeline': {'disableMulticolor': true}}}%%
-timeline
-    section Phase 1 - Foundation (2026)
-        Q1-Q2 : Monitoring system enhancements<br>Critical service optimizations
-        Q3-Q4 : Storage performance improvements<br>DiracX readiness assessment
-    section Phase 2 - Scaling (2027)
-        Q1-Q2 : Network infrastructure upgrades<br>Compute resource expansion
-        Q2-Q3 : Containerization pilot projects<br>Storage system procurement
-        Q3-Q4 : Advanced orchestration deployment<br>Network upgrade completion
-    section Phase 3 - Transformation (2028)
-        Q1-Q2 : DiracX migration completion<br>Production migration approval
-        Q2-Q3 : Full system validation<br>Advanced monitoring implementation
-        Q3-Q4 : Performance optimization<br>Scalability validation
-```
+Services of DIRAC v9 and DiracX will need to live together for some time
+
+<Arrow x1="300" y1="170" x2="370" y2="170" />
+<!-- <Line :x1=345 :y1=200 :x2=345 :y2=500 :width=1 /> -->
+
+<Arrow x1="610" y1="170" x2="680" y2="170" />
+<!-- <Line :x1=633 :y1=200 :x2=633 :y2=500 :width=1 /> -->
+
+<div style="display: flex; align-items: center; justify-content: center;">
+    <img id="D_X" src="/public/images/legacy_before_Adaptor.png" class="mx-auto w-1/4"> </img>
+    <img id="D_Ad" src="/public/images/legacyAdaptor.png" class="mx-auto w-1/4"> </img>
+    <img id="X" src="/public/images/legacy_after_Adaptor.png" class="mx-auto w-1/4"> </img>
+</div>
+
+<SpeechBubble position="r" color='cyan' shape="round"  v-drag="[100,350,40,60]">
+1
+</SpeechBubble>
+
+<SpeechBubble position="r" color='cyan' shape="round"  v-drag="[370,350,40,60]">
+2
+</SpeechBubble>
+
+<SpeechBubble position="r" color='cyan' shape="round"  v-drag="[660,350,40,60]">
+3
+</SpeechBubble>
+
+<SpeechBubble position="t" color='amber' shape="round"  v-drag="[160,350,120,180]">
+DIRAC and DiracX share the databases
+</SpeechBubble>
+
+<SpeechBubble position="t" color='amber' shape="round"  v-drag="[430,350,160,180]">
+A legacy adaptor moves traffic from DIRAC to DiracX services
+</SpeechBubble>
+
+<SpeechBubble position="t" color='amber' shape="round"  v-drag="[720,350,120,140]">
+DIRAC services can be removed
+</SpeechBubble>
 
-<!-- ## JUNO DCI System Evolution Plan -->
-<!--  -->
-<!-- ### Hardware Infrastructure -->
-<!-- - **Compute Resources**: Expand GPU capabilities for ML workloads -->
-<!-- - **Storage Systems**: Upgrade to high-performance parallel file systems -->
-<!-- - **Network Fabric**: Implement dedicated science DMZ connections -->
-<!--  -->
-<!-- ### Software Stack -->
-<!-- - **Dirac Evolution**: Complete migration from DIRAC v8 to DiracX -->
-<!-- - **Containerization**: Full Docker/Kubernetes deployment for all services -->
-<!-- - **Orchestration**: Advanced workflow management and automation -->
-<!--  -->
-<!-- ### Architecture Optimization -->
-<!-- - **Microservices**: Decompose monolithic services into scalable components -->
-<!-- - **Data Management**: Implement tiered storage with intelligent caching -->
-<!-- - **Monitoring**: AI-driven predictive analytics and anomaly detection -->
-<!--  -->
-<!-- ### Key Objectives -->
-<!-- 1. **Scalability**: Support 5x current workload capacity -->
-<!-- 2. **Reliability**: Achieve 99.9% system availability -->
-<!-- 3. **Performance**: Reduce average job completion time by 50% -->
-<!-- 4. **Maintainability**: Simplify operations and reduce manual intervention -->
 
 ---
 layout: top-title-two-cols