[
https://issues.apache.org/jira/browse/MESOS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Vivien updated MESOS-1618:
-----------------------------------
Description:
The idea is a specialized server process (mesos-compat) whose sole purpose is
to exercise and validate mesos framework clients. This is to help future
implementers of pure framework clients (implemented in their native language)
to test their compatibility with mesos server regardless of internal
implementation strategies used.
Process mesos-compat
* As mentioned this is a specialized mock master server
* Exposes all of the regular HTTP service paths the master handles
* Also exposes additional HTTP service paths that must be called in a scheduler
being tested to report states, updates, metrics, etc.
How It Would Work
* Process mesos-compat exposes a URL (similar to a mesos-local)
* Developers would create a specialized SchedDriver and Scheduler to execise
the test suites.
* Client would connect to the master URL and attempt to do all the natural
activities a framework does for maximum coverage of cases
* Client would use the additional HTTP service calls to report needed states,
etc.
* mesos-compat would gather data and validate states as tests runs.
Again, this is a rough idea. I don't even know if it makes sense or if it
would even work. It will require numerous input/feedback from all before it can
become something that can actually be done.
was:
The idea is a specialized server process (mesos-compat) whose sole purpose is
to exercise and validate mesos framework clients. This is to help future
implementers of pure framework clients (implemented in their native language)
to test their compatibility with mesos server regardless of internal
implementation strategies used.
Process mesos-compat
* As mentioned this is a specialized mock master server
* Exposes all of the regular HTTP service paths the master handles
* Also exposes additional HTTP service paths that must be called in a scheduler
being tested to report states, updates, metrics, etc.
How It Would Work
* Process mesos-compat exposes a URL (similar to a mesos-local)
* Developers would create a specialized SchedDriver and Scheduler to execise
the test suites.
* Client would connect to the master URL and attempt to do all the natural
activities a framework does for maximum coverage of cases
* Client would use the additional HTTP service calls to report needed states,
etc.
* mesos-compat would gather data and validate states as tests runs.
Again, this is a rough idea. I don't even know if it makes sense. It will
require numerous input/feedback from all before it can become something that
can actually be done.
> Component to test/validate Apache Mesos Framework Clients
> ---------------------------------------------------------
>
> Key: MESOS-1618
> URL: https://issues.apache.org/jira/browse/MESOS-1618
> Project: Mesos
> Issue Type: Epic
> Components: general, test
> Reporter: Vladimir Vivien
> Priority: Minor
>
> The idea is a specialized server process (mesos-compat) whose sole purpose is
> to exercise and validate mesos framework clients. This is to help future
> implementers of pure framework clients (implemented in their native language)
> to test their compatibility with mesos server regardless of internal
> implementation strategies used.
> Process mesos-compat
> * As mentioned this is a specialized mock master server
> * Exposes all of the regular HTTP service paths the master handles
> * Also exposes additional HTTP service paths that must be called in a
> scheduler being tested to report states, updates, metrics, etc.
> How It Would Work
> * Process mesos-compat exposes a URL (similar to a mesos-local)
> * Developers would create a specialized SchedDriver and Scheduler to execise
> the test suites.
> * Client would connect to the master URL and attempt to do all the natural
> activities a framework does for maximum coverage of cases
> * Client would use the additional HTTP service calls to report needed states,
> etc.
> * mesos-compat would gather data and validate states as tests runs.
> Again, this is a rough idea. I don't even know if it makes sense or if it
> would even work. It will require numerous input/feedback from all before it
> can become something that can actually be done.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
