[
https://issues.apache.org/jira/browse/MESOS-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu updated MESOS-2067:
-----------------------------
Description:
Based on MESOS-1474, we'd like to provide an HTTP API on the master for the
maintenance primitives in mesos.
For the MVP, we'll want something like this for manipulating the schedule:
{code}
/maintenance
GET - returns the schedule, which will include the various maintenance
windows.
POST - create or update the schedule with a JSON blob (see below).
/maintenance/status (Note: the slash might not be usable)
GET - returns a list of machines and their maintenance mode.
POST - change the mode of a list of machines.
The request would have a query parameter to express the action of
starting or stopping maintenance.
{code}
A schedule might look like:
{code}
{
"windows" : [
{
"machines" : ["192.168.0.1", "localhost", "foo.bar.com", ... ],
"unavailability" : {
"start" : 12345, // Epoch seconds.
"duration" : 1000 // Seconds.
}
},
...
]
}
{code}
There should be firewall settings such that only those with access to master
can use these endpoints.
was:
Based on MESOS-1474, we'd like to provide an HTTP API on the master for the
maintenance primitives in mesos.
Something like this for manipulating the schedule:
* GET /maintenance: returns the schedules and status
* POST /maintenance: an array of hosts
* DELETE /maintenance/schedule: clear the schedule(s)
There should be firewall settings such that only those with access to master
can use these endpoints.
> Add HTTP API to the master for maintenance operations.
> ------------------------------------------------------
>
> Key: MESOS-2067
> URL: https://issues.apache.org/jira/browse/MESOS-2067
> Project: Mesos
> Issue Type: Task
> Components: master
> Reporter: Benjamin Mahler
> Assignee: Artem Harutyunyan
> Labels: mesosphere, twitter
>
> Based on MESOS-1474, we'd like to provide an HTTP API on the master for the
> maintenance primitives in mesos.
> For the MVP, we'll want something like this for manipulating the schedule:
> {code}
> /maintenance
> GET - returns the schedule, which will include the various maintenance
> windows.
> POST - create or update the schedule with a JSON blob (see below).
> /maintenance/status (Note: the slash might not be usable)
> GET - returns a list of machines and their maintenance mode.
> POST - change the mode of a list of machines.
> The request would have a query parameter to express the action of
> starting or stopping maintenance.
> {code}
> A schedule might look like:
> {code}
> {
> "windows" : [
> {
> "machines" : ["192.168.0.1", "localhost", "foo.bar.com", ... ],
> "unavailability" : {
> "start" : 12345, // Epoch seconds.
> "duration" : 1000 // Seconds.
> }
> },
> ...
> ]
> }
> {code}
> There should be firewall settings such that only those with access to master
> can use these endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
