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 2017/01/17 19:01:26 UTC

[jira] [Closed] (FLINK-4899) Implement DCOS package

     [ https://issues.apache.org/jira/browse/FLINK-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eron Wright  closed FLINK-4899.
-------------------------------
    Resolution: Duplicate

Closing in favor of sub-tasks in FLINK-5533.

> Implement DCOS package
> ----------------------
>
>                 Key: FLINK-4899
>                 URL: https://issues.apache.org/jira/browse/FLINK-4899
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cluster Management, Mesos
>            Reporter: Eron Wright 
>            Assignee: Eron Wright 
>             Fix For: 1.2.0
>
>
> Implement a DCOS package to install Flink.   Some implementation goals:
> - Install a traditional Flink cluster as a DCOS service (i.e. a single appmaster leveraging the Mesos resource manager).
> - Ensure the service name is customizable, to allow for numerous clusters.  Use the service name (default Flink) in the `high-availability.namespace` setting.
> - Provide the web UI via the DCOS admin router.    
> - Expose the JM endpoint (and other endpoints) as service ports (e.g. `$PORT0`).
> - Prepare and use a Docker image, i.e `dcos-flink`, as the basis for the JM and the TM.
> - Configure the ZK connection info as normal for a DCOS service.
> No further DCOS CLI integration is expected in the initial release.   The normal `flink run` command (operating in 'standalone' mode) should suffice to use the service.    Note that the command will probably work only from within the cluster (since it must connect to ZK and to the JM service port).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)