You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Eron Wright (JIRA)" <ji...@apache.org> on 2018/06/19 20:44:00 UTC
[jira] [Commented] (FLINK-9611) Allow for user-defined artifacts to
be specified as part of a mesos overlay
[ https://issues.apache.org/jira/browse/FLINK-9611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517528#comment-16517528 ]
Eron Wright commented on FLINK-9611:
-------------------------------------
I really like this idea, except for the proposed name because it has a connotation of overlaying the 'user' (which is sort of what happens with the Kerberos overlay). Maybe 'MesosCustomOverlay'.
> Allow for user-defined artifacts to be specified as part of a mesos overlay
> ---------------------------------------------------------------------------
>
> Key: FLINK-9611
> URL: https://issues.apache.org/jira/browse/FLINK-9611
> Project: Flink
> Issue Type: Improvement
> Components: Configuration, Docker, Mesos
> Affects Versions: 1.5.0
> Reporter: Addison Higham
> Priority: Major
>
> NOTE: this assumes mesos, but this improvement could also be useful for future container deployments.
> Currently, when deploying to mesos, the "Overlay" functionality is used to determine which artifacts are to be downloaded into the container. However, there isn't a way to plug in your own artifacts to be downloaded into the container. This can cause problems with certain deployment models.
> For example, if you are running flink in docker on mesos, you cannot easily use a private docker image. Typically with mesos and private docker images, you specify credentials as a URI to be downloaded into the container that give permissions to download the private image. Typically, this credentials expire after a few days, so baking them into a docker host isn't a solution.
> It would make sense to add a `MesosUserOverlay` that would simplify take some new configuration parameters and add any custom artifacts (or possibly also environment variables?)
> Another solution (or longer term solution) might be to allow for dynamically loading an overlay class for even further customization of the container specification.
>
>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)