Update Mount for CacheRuntime

Signed-off-by: xliuqq <xlzq1992@gmail.com>

Author: xliuqq

proposals/runtime/v1.1.0_extend_cache_runtime/full_cache_runtime.md

@@ -63,12 +63,33 @@ Cache Runtime 为缓存系统提供 RuntimeConfig，因此Curvine 组件需要**
 
 - 不同于curvine，Juicefs 是无Master架构，在[启动时就执行 format ](https://juicefs.com/docs/zh/community/getting-started/for_distributed/#4-创建文件系统)，只支持一个远程存储，因此直接在 worker/fuse 的启动命令里执行；
 
+扩展 CacheRuntimeClass 定义，增加对 mount UFS 的支持
+
+```go
+type CacheRuntimeClass struct {
+    // 当前 Cache System 支持哪些数据操作
+    LifeCycleHook *LifeCycleHook `json:"lifeCycleHook,omitempty"`
+}
+type LifeCycleHook struct { 
+    // 挂载 UFS 的 hook 操作，针对 Master-Slave 架构，需要在 Master 中执行
+    MountUfs *MountUfs  `json:"mountUfs,omitempty"`
+}
+type MountUFS struct {
+    // 执行的命令，必选，会在 Master Pod 中执行
+    Command string `json:"command"`
+    
+    // 执行命令的超时时间（单位：秒），最小值为 5s.
+    Timeout int `json:"timeout,omitempty"`
+}
+```
+
 Curvine Cache Runtime 的处理流程如下图所示：本项工作的重点在于：
 
 1. 提供启动脚本，将 Fluid 提供的 RuntimeConfig 转化为 Curvine 所使用的配置文件；
    - 拟采用 go template 要求的格式定义 Curvine 的配置文件，并进行替换；
 1. 添加 Mount UFS 步骤，在 Master Sts 启动完成后，进入 Master Pod 执行 cv mount 操作；
-   - mount 操作由缓存系统定义在ConfigMap中并挂载到 Master Pod 中。
+   - **mount 操作在 CacheRuntimeClass 中定义，指定在特定的角色（如Master）的Pod 中执行指定的命令，以RuntimeConfig文件为参数。**
+   - 对于 JuiceFS 缓存系统，不需要单独执行 mount 参数，在 CacheRuntimeClass 中不定义即可；
 
 ![img](./pics/curvine_integration.jpeg)
 
@@ -83,19 +104,18 @@ type CacheRuntimeClass struct {
 }
 
 type DataOperationSpec struct {
-    // 数据操作，如 DataLoad, DataBackup, DataMigration等
+    // Data Operation，如 DataLoad, DataBackup, DataMigration等
     // +kubebuilder:validation:Enum=DataLoad
-    Name string `json:"string"`
+    Name string `json:"name,string"`
 
-    // DataOperation 所使用的镜像版本，避免从 Master Pod 的 Container 中解析
-    // +kubebuilder:validation:Required
-    Image string `json:"image,omitempty"`
-
-    // Command for DataOperation Pod
+    // The image name for DataOperation executing
+    Image string `json:"name,string"`
+    
+    // Command for image container
     Command []string `json:"command,omitempty"`
-
-    // Args for DataOperation Pod
-    Args []string `json:"args,omitempty"
+    
+    // Args for image container
+    Args []string `json:"args,omitempty" 
 }
 ```
 
@@ -122,8 +142,16 @@ type DataOperatorYamlGenerator interface {
 
 针对 operation 的 不同 Type，做不同的处理。DataProcess 不区分缓存系统，可以复用现有的 Helm Yaml 生成逻辑；而其它的 DataOperation 都需要相应的缓存系统镜像及其配置。
 
-- 通过新增的 DataOperationSpec 定义构建 Pod，并挂载 RuntimeConfig 和相应DataOperation的Config；
+- 通过新增的 DataOperationSpec 定义相应 Pod ，启动并执行相应的数据操作的命令，其中 Fluid DataOperation的相关配置信息，会挂载到 /etc/fluid/config/dataop 文件中；
 
-- Pod 的启动命令形式类似："/bin/sh -c  generate_conf.sh /etc/fluid/config/runtime && /entrypoint.sh /etc/fluid/config/dataop"，包括配置转换和缓存实际数据操作命令；
 
 ### 3. 支持 In-Place Upgrade 和 ReBuild
+
+版本更新时的原地升级：
+
+
+
+配置更新时的缓存重建：
+
+
+

roadmap/v1.1.0_extend_cache_runtime .md

@@ -2,7 +2,7 @@
 
 ## 1. Overview
 
-本文概述了扩展 Generic Cache Runtime 接口工作的实施路线图，旨在提供更简便的缓存系统集成方式和更高的缓存可用性。更详细的设计文档见 XXX。
+This article outlines the implementation roadmap for extending the Generic Cache Runtime interface, aiming to provide a simpler way to integrate caching systems and enhance cache availability. For a more detailed design document, please refer to [the proposal](../proposals/runtime/v1.1.0_extend_cache_runtime/full_cache_runtime.md)。
 
 ### 1.1. Problem Statement
 
@@ -12,22 +12,22 @@ In production scenarios, it is necessary to support In-Place upgrade for engine
 
 ### 1.2. Solution Summary
 
-扩展 Cache Runtime 接口，使用 Curvine/Alluxio 作为缓存系统示例，实现：
+Extend generic  cache runtime interface to achieve：
 
 - Curvine Integration：Implement working reference adapters for Curvine；
 - DataOperation Support ：Implement DataOperation interface including DataLoad and DataOperation for cache runtime；
 - In-Place upgrade and rebuild：Implement  in-place upgrade for engine version update  and in-place cache rebuild after node failure or config change.
 
 ### 1.3. Goals
 
-- 通过完善 GenericCacheRuntime 降低第三方缓存系统的集成难度，提升代码质量；
-- 支持缓存系统的在线升级，不中断服务，提高系统可用性，满足生产级要求；
+- Reduce the integration difficulty of third-party caching systems and enhance code quality by improving Generic Cache Runtime;
+- Support in-place upgrades for the caching system without interrupting services, improve system availability, and meet production-level requirements;
 
 ## 2. Phase
 
 ### Phase 1: Curvine Integration 
 
-目标：完成 Cache Runtime 的数据缓存功能，完成与 Curvine 的联调测试，编写单元测试、e2e单元测试和集成文档。
+**Objectives**: Complete the data caching function of Cache Runtime, conduct joint debugging and testing with Curvine, and write unit tests, e2e unit tests, and integration documentation.
 
 | Task | Description                                                  | Deliverable                                                  |
 | ---- | ------------------------------------------------------------ | ------------------------------------------------------------ |
@@ -38,7 +38,7 @@ In production scenarios, it is necessary to support In-Place upgrade for engine
 
 ### Phase 2: DataOperation Support
 
-目标：Cache Runtime 支持 DataOperation（包括DataLoad、DataProcess），编写单元测试、e2e单元测试和集成文档。
+Objective: Cache Runtime supports DataOperation (including DataLoad, DataProcess), and write unit tests, e2e unit tests, and integration documentation.
 
 | Task | Description                                              | Deliverable                                                  |
 | ---- | -------------------------------------------------------- | ------------------------------------------------------------ |
@@ -52,23 +52,40 @@ In production scenarios, it is necessary to support In-Place upgrade for engine
 
 ### Phase 3: In-Place Upgrade and Rebuild
 
-目标：支持缓存系统的 In-Place 的升级和重建
+Objective: To support in-place upgrades during the version upgrade of the caching system and cache rebuilding during configuration changes.
 
-| Task | Description                             | Deliverable |
-| ---- | --------------------------------------- | ----------- |
-| 1.1  | Support engine version in-place upgrade |             |
-| 1.2  |                                         |             |
-| 1.3  |                                         |             |
-| 1.4  |                                         |             |
+| Task | Description                                                  | Deliverable                                         |
+| ---- | ------------------------------------------------------------ | --------------------------------------------------- |
+| 1.1  | Support in-place upgrade for updating engine version         | Cache Runtime supports in-place upgrade             |
+| 1.2  | Support in-place cache rebuild for config changes            | Cache Runtime supports in-place cache rebuild       |
+| 1.3  | Write related unit test code and e2e test scripts            | unit tests and e2e test using curvine cache runtime |
+| 1.4  | Document how to use in-place upgrade and in-place cache rebuild | Docs section: "In-Place Upgrade and Rebuild".       |
 
 
 
-## 3. 时间线
+## 3. Dependencies 
+
+- No new external service dependencies at build time.
+
+
+
+## 4. Success Metrics
+
+**Usability**: users can utilize Curvine for data caching through GenericCacheRuntime.
+
+**Support**: users can use Curvine for DataLoad/DataProcess scenarios.
+
+**Resilience**: users can update Curvine Cache Runtime version and rebuild cache in-place.
+
+
+
+## 5. **Timeline (Suggested)**  
 
 | **Phase**   | **Focus**                    | **Suggested duration** |
 | ----------- | ---------------------------- | ---------------------- |
 | **Phase 1** | Curvine Integration          | 3-4 Weeks              |
 | **Phase 2** | DataOperation Support        | 3-4 Weeks              |
 | **Phase 3** | In-Place Upgrade and Rebuild | 3-4 Weeks              |
 
-Total: on the order of  **9-12 weeks** for a small team or single contributor, depending on familiarity with the codebase and cluster access for testing.
+Total: on the order of  **9-12 weeks** for a small team or single contributor, depending on familiarity with the codebase and cluster access for testing.
+