You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: