ciscocloud / exhibitor-mesos-framework Goto Github PK

Currently tasks are named like exhibitor-$id-$hostname-$port which is excessive because folks will either use mesos-dns and will want to use something similar to exhibitor-1.marathon.mesos or may just get endpoint URLs from cluster status.

Task IDs are currently exactly the same but this approach will fail if 2 scheduler instances in one cluster will spawn servers with same ids

This is a part of DCOS specification pre-alpha requirements.

This is a part of DCOS specification pre-alpha requirements.

This is a part of DCOS specification pre-alpha requirements.

This is a part of DCOS specification pre-alpha requirements.

CLI should be able to work with id ranges, e.g. "add 0..5", "stop 1..3,6" etc.

Serve the file, fill shared configuration. (maybe something else if needed)

This is a part of DCOS specification pre-alpha requirements.

This one might be tricky because Exhibitor uses jps calls internally so java should be exported properly.

This is a part of DCOS specification pre-alpha requirements.

Port ranges to accept should be configurable (e.g. 31050..31100 or 32613 etc) so we could decline offers that do not satisfy this condition.

This is a part of DCOS specification pre-alpha requirements.

e.g. group by, cluster (https://github.com/mesosphere/marathon/blob/master/docs/docs/constraints.md for reference)

This is a part of DCOS specification pre-alpha requirements.

This is probably already implemented but should probably be rechecked to make sure it is.