You can now install packages from the DC/OS Universe with a single click in the web interface. The packages can be installed with defaults or customized directly in the UI. For more information, see the documentation.
You can monitor the health of your cluster components from the DC/OS web interface. The component health page provides the health status of all DC/OS system components that are running in systemd. You can drill down by health status, host IP address, or specific systemd unit. For more information, see the documentation.
Applications and Search Improved global search with better ranking (fuzzy matching). Groups are now shown as part of search results too. Application list support for browsing empty groups. Create empty groups directly from the UI. A new sidebar filter to match apps with attached volumes.
Create and Edit form improvements Redesigned form with improved usability. We added a completely new JSON editor. Create resident tasks with persistent local volumes from the UI. Greatly simplified port management.
Support for Persistent Storage You can now launch tasks that use persistent volumes by specifying volumes either via the UI or the REST API. Marathon will reserve all required resources on a matching agent, and subsequently launch a task on that same agent if needed. Data within the volume will be retained even after relaunching the associated task.
Support for Scheduler Upgrades Schedulers are specific applications to Marathon, since they can also launch tasks. A deployment in Marathon for upgrading schedulers also includes the migration of all tasks the scheduler has started via a protocol.
Support for Ports Metadata The v2 REST API was extended to support additional ports metadata (protocol, name, and labels) through the portDefinition application field. Marathon will pass this new information to Mesos, who will in turn make it available for service discovery purposes.
Support for HTTP based plugin extensions Plugins can now implement HTTP endpoints.
Updated Auth plugin interface The Authentication and Authorization plugin interface was redesigned in order to support more sophisticated plugins.
Added a leader duration metric The metrics now include a gauge that measures the time elapsed since the last leader election happened. This is helpful to diagnose stability problems and how often leader election happens.
Better error messages API error messages are now more consistent and easier to understand for both humans and computers.
Improved Task Kill behavior in deployments by performing kills in batches When stopping/restarting an application, Marathon will now perform the kills in batches, in order to avoid overwhelming Mesos. Support the
TASK_KILLING state available in Mesos 0.28.
Support for Authentication and Authorization It is now possible to authorize operations to applications in Marathon. The authentication service in DC/OS allows defining actions that users are allowed to perform on applications. Marathon will enforce those rules.
For the full set of changes, please refer to the Marathon Release Notes.
exhibitor_storage_backend: shared_filesystem), you must use the Manual command line installation method.
agent_list must be provided along with master_list.
mesos.masterA records as well as
leader.mesos:5050/slavesto get the complete list of hosts in the cluster. This system has a known bug where an agent will not show up in the list returned from
leader.mesos:5050/slavesif the Mesos slave service is not healthy. This means the system health API will not show this host. If you experience this behavior it's most likely because your Mesos slave service on the missing host is unhealthy.
slave_publicrole for public agents is changing to
Persistent local volumes With Docker, the containerPath must be relative and will always appear in
/mnt/mesos/sandbox/. If your application (e.g. a DB) needs an absolute directory this won’t work.
Authorization - In this release we have perimeter security & auth, but not internal auth. Requests originating in the cluster - i.e. that don’t have an auth token issued by AdminRouter - are not subject to authorization. Example: Marathon-LB running on DC/OS will work as expected against a Marathon with Security Plugin enabled: It will see all apps despite not having authentication credentials.