[
https://issues.apache.org/jira/browse/SUBMARINE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121444#comment-17121444
]
Wangda Tan commented on SUBMARINE-507:
--------------------------------------
[~ztang], good point, here's my thoughts:
{quote}Will the kernel spec has hard dependencies on the conda component
versions when enabling?
{quote}
Based on the Anaconda's typical usage, version of Python is part of the kernel,
so in that case. Python inside the image will be ignored. (Anaconda uses
environment variables to only pass whatever libraries when the kernel is
activated).
{quote}[~wangda], for the kernel spec, is the sample spec generated by "condo
export"? It seems hard to write that by hand.
{quote}
That's correct, ideally user should not write the spec. Once a kernel is
activated, all the activities like {{pip install}} will be tracked and when
user call {{conda export}} such changes will be part of the exported conda spec.
> Submarine Environment Management
> --------------------------------
>
> Key: SUBMARINE-507
> URL: https://issues.apache.org/jira/browse/SUBMARINE-507
> Project: Apache Submarine
> Issue Type: New Feature
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
> Labels: pull-request-available
>
> Scope of this JIRA is to support environment management. It includes the
> following:
> 1. Create Environment
> 2. Update Environment
> 3. Delete Environment
> 4. List Environments
> In addition, this JIRA should also ensures that environments has been
> persisted like experiments so that it can used for later use.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@submarine.apache.org
For additional commands, e-mail: dev-h...@submarine.apache.org
