Task Summary
Currently, Python Virtual Environments (PVEs) are tied to the lifecycle of the Computing Unit (CU) in which they are created. As a result, when a CU is terminated, all associated PVEs are deleted as well.
This design proposes decoupling PVEs from individual CUs by persisting PVE metadata and configuration in the database. PVEs would become reusable resources that exist independently of any specific CU. When a workflow requires a particular PVE, the environment can be provisioned or installed on the target CU as needed for execution.
Task Type
Task Summary
Currently, Python Virtual Environments (PVEs) are tied to the lifecycle of the Computing Unit (CU) in which they are created. As a result, when a CU is terminated, all associated PVEs are deleted as well.
This design proposes decoupling PVEs from individual CUs by persisting PVE metadata and configuration in the database. PVEs would become reusable resources that exist independently of any specific CU. When a workflow requires a particular PVE, the environment can be provisioned or installed on the target CU as needed for execution.
Task Type