Skip to content
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.

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

Timestamp for phases in plan #411

Open
andlaz opened this issue Mar 7, 2017 · 1 comment
Open

Timestamp for phases in plan #411

andlaz opened this issue Mar 7, 2017 · 1 comment

Comments

@andlaz
Copy link

andlaz commented Mar 7, 2017

Hello,

i was wondering if you see at least a "started_at" ( and preferably a "completed_at", if that makes sense for all phases.. ) timestamp as feasible/useful to be added to the phase object in plans..

My use case is enforcing a timeout around deployment of the framework from within a piece of software that wraps around DC/OS apis/products ( cosmos, metronome, marathon.. etc ) to CRUD cassandra framework instances. Often in a resource-starved scenario we get a bunch of deployments hanging around waiting for suitable offers and blocking this application upstream.

thanks,
Andras

@triclambert
Copy link
Contributor

This repo is deprecated and will be archived in one week. Please see the latest version of Cassandra or DSE for DC/OS:

https://docs.mesosphere.com/service-docs/cassandra/
https://docs.mesosphere.com/service-docs/dse/ (enterprise-only)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants