New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Run Chronos via Marathon #2

Open

jonas opened this issue Nov 24, 2015 · 0 comments

Labels

Contributor

jonas commented Nov 24, 2015

Motivation

Improve monitoring and recovery.

Input

Installing Chronos as DCOS package: https://docs.mesosphere.com/services/chronos/
DCOS Chronos package files: https://github.com/mesosphere/universe/tree/version-1.x/repo/packages/C/chronos/2
Apollo DCOS role: https://github.com/Capgemini/Apollo/tree/master/roles/dcos_cli

Output

Chronos role updated to run via Marathon
-- Installed via DCOS or some a custom docker image
Chronos UI is accessible on edge-node using HTTP basic or internally via chronos.marathon.mesos

Test

Chronos is shown in Marathon UI
dig chronos.marathon.mesos should resolve to a node IP
Chronos UI is accessible on edge-node or via SSH port forwarding

The text was updated successfully, but these errors were encountered:

jonas added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment