1. Progress Report 8/26

2. CHT Project Develop a resource management scheduling algorithm for CHT datacenter. ◦ Meet the SLA of jobs.  Two types of jobs, interactive/latency-sensitive and batch/computation-intensive.  A job consists of several independent tasks.

3. Target Platform CHT datacenter ◦ Heterogeneous servers Openshift ◦ Red Hat's Platform-as-a-Service (PaaS) that allows developers to quickly develop, host, and scale applications in a cloud environment. ◦ Based on Kubernetes  Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops.

4. Idea Borrow the idea from Heracles ◦ A feedback-based controller that enables the safe collocation of best-effort tasks alongside a latency-critical service. One interactive task per server. ◦ Monitor the status of interactive tasks.  Loading, QoS …etc. ◦ Deploy batch tasks to servers with low- loading interactive task.

5. Pseudo Code 1. if(newTask.type == LC):# new task is an interactive task 2.target <- find a server with only batch tasks 3.if(target == NULL): 4.target = newServer() 5. else:# new task is a batch task 6.candidate <- a list of servers with low-loading interactive task 7.if(empty(candidate)): 8.target = newServer() 9.else: 10.target <- maxScore(candidate) 11. deploy newTask to target

6. Idea(Cont.) A monitoring agent/controller on every server. ◦ Periodically report server status. ◦ Decide whether this server can accommodate more batch tasks.  To be a “candidate” during task deployment. ◦ Release batch tasks while the loading of the interactive task increases.  Release tasks are treated as new tasks and will trigger the deployment process.

7. Some Issues Measuring the loading of interactive jobs ◦ Insert agents inside the container.  Developer (of the job) should provide such agent. ◦ Periodically report to the resource management system. Measuring the performance of batch jobs ◦ Throughput.

8. Some Issues(Cont.) Size of container ◦ Fixed for the same job. ◦ Varies among different jobs. Score function of server ◦ Assign batch tasks to the server with the highest score.

9. Q1 Review Openshift ◦ (1) 目前 survey 狀況 ◦ (2) 是否要採用 Openshift ◦ (3) 若需採用要如何介接，後續的廠商 support ( 鄭博在意的問 題 ) 動態分配政策演算法 ◦ (1) 確認演算法設計的前提 (ex: non-preemptive job, equally- sized job, etc…) ◦ (2) 確認演算法所需的 input 資料項目 如何實證 ◦ (1) CHT 擬提供兩組 docker image  a. 一組 image 提供 interactive 測試程式 ( 跑在 JBoss EAP 上 )  b. 一組 image 提供 batch 轉檔程式 及 資料產製程式 ( 產製用來轉檔 的 input) 其他 Kick-off meeting 追蹤事項

10. Next Prepare for the Q1 review on 9/3(Thu.)