[
https://issues.apache.org/jira/browse/SUBMARINE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120732#comment-17120732
]
Zhankun Tang commented on SUBMARINE-507:
----------------------------------------
[~maniraj...@gmail.com], yeah. We've already published the
"apache/submarine:mini-0.3.0" under "apache/submarine" repo. We can release
more.
[~wangda], for the kernel spec, is the sample spec generated by "condo export"?
It seems hard to write that by hand.
Will the kernel spec has hard dependencies on the conda component versions when
enabling?
For instance, we provide a submarine image with "anaconda=2019.02=py36", but
the kernel spec is "2020.02=py37". Will the image fail to start due to version
mismatch?
In other words. Is the kernel spec portability a concern for us?
{code:java}
- anaconda=2020.02=py37_0
- anaconda-client=1.7.2=py37_0
- anaconda-navigator=1.9.12=py37_0
{code}
> 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
