[ 
https://issues.apache.org/jira/browse/SUBMARINE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120450#comment-17120450
 ] 

Manikandan R commented on SUBMARINE-507:
----------------------------------------

Thanks for sharing your views.

IIUC, We would like to have only 1 table "environments" in Submarine Metastore. 

Few more questions:

1. How do we decide that we need to talk to Docker hub's "apache/submarine" or 
end-user's existing Docker registry? Using docker image name?
2. For both the categories, Can we safely assume images will be always 
available for use at run time? Nothing to worry about this while creating 
environment.
3. For first category of base images ("apache/submarine"),When & How are we 
going to create images and release to "apache/submarine"? Using docker file 
manually? Admin would be doing this?
4. For second category of base images, Can we assume end users would have 
created the image in their docker registry?
5. It seems we are in favour of storing environment spec as is in a string 
based column in "environments" table?
6. conda env activation happens at run time while running the notebook or 
experiment. When are we going to create an env in conda? 

> 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

Reply via email to