[
https://issues.apache.org/jira/browse/SUBMARINE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119816#comment-17119816
]
Wangda Tan commented on SUBMARINE-507:
--------------------------------------
Thanks [~maniraj...@gmail.com], [~ztang] for the comments,
For the environment, I don't think we should get into image storage / Docker
registry setup business, it should just be a Docker image name and K8s can
figure out what credentials to pull the docker image based on secrets stored in
the namespace. And users are responsible for setting up Docker registry and K8s
secrets.
{quote}For base image storage, one simple way, to begin with, might be storing
the submarine base image or release them in Docker hub's "apache/submarine".
And build an entry script to activate the conda spec at runtime.
{quote}
This make sense to me, and this is just an example, user can choose whatever
base Docker image they want to use, it could borrow from the apache/submarine's
base image.
{quote}For end-user custom base image storage, I'd prefer that we can integrate
the end-user's existing Docker registry as a starting.
{quote}
Make sense.
One thing I realized is, if user only want to use a Docker image (instead of
Anaconda), asking users to create an environment, and put Docker image like:
{code:java}
Environment:
name: my-env
docker-image: example.com/my-docker-image:0.1.2
In experiment, user specify
Experiment:
name: "My-tf-job"
environment: "my-env"
task:
script: ...
resource: ...{code}
It is purely an overhead and bad user experiences.
How about we can provide a short cut to specify an "anonymous/embeded
Environment" as part of the Experiment, for example:
{code:java}
Experiment:
name: "My-tf-job"
environment: "my-env" // point to a "named" environment, or
environment:
docker-image: example.com/my-docker-image:0.1.2
kernel-name: ...
task:
script: ...
resource: ... {code}
If it is possible, we should make the "embedded environment" be part of 0.4.0
itself, so we don't have to change this API when we release 0.5.0
Thoughts? [~ztang], [~maniraj...@gmail.com]
> 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
