agent-substrate / agent-substrate/substrate

How to patch CVEs and upgrade gVisor / microVM version used by SandboxConfig?

未關閉
#587 1 則留言 0 個 reaction 已指派 2 人 已被 @zoez7 認領 在 GitHub 檢視
area/api area/gvisor area/microVM kind/feature
主要語言
Go
星號
1.8k
分支
316
平均合併
2 天 43 分鐘
30 天內合併 PR
287

描述

Some thoughts on this when working on Actor Upgrades (https://github.com/agent-substrate/substrate/issues/477):

* Upgrading gVisor or microVM means that the Actor's previous memory snapshot is not going to be usable. ResumeActor with new runsc version must use a new golden memory snapshot (or cold boot). Therefore, each ActorTemplateVersion must specify the exact SandboxConfig it uses, and the config must remain imutable.

* Different persona that manages SandboxConfig and ActorTemplate (the deployment). Although the memory snapshot means that "SandboxConfig" impacts the lifecycle of Actors. The configuration of "which runsc binary to use" belongs to the Platform Engineer layer, where as "ActorTemplate" belongs to the Agent Developer layer. Today in substrate we have a cluster-wide default SandboxConfig, which decouples it away from the ActorTemplate definition, and I think it makes sense from a Actor Developer's perspective. Having to define the exact CHV version that the AT runs on is not a good user experience.

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。