Release notes for Beta DC/OS Storage Service version 0.6.0
- This version of the DC/OS Storage Service requires DC/OS Enterprise version 1.13 or later.
- Volume capacity constraints may be specified as part of a volume profile.
- Added and enhanced existing CLI commands to support mitigation of issues resulting from agent reconfiguration events.
- SDK-based services (still in Beta) may consume DC/OS Storage Service volumes.
- Storage provider configurations may be modified in place, and no longer require a remove/reinstall cycle in order to update.
- Storage plugins are upgradable in-place, and no longer require a remove/reinstall cycle in order to upgrade.
- Storage service diagnostics are downloaded as part of the DC/OS Diagnostics bundle.
- Narrowed the scope of Mesos disk permissions required by the storage service.
- Devices provider is not removable if another provider (e.g. LVM provider) is consuming one or more of its devices.
- Improved observability via additional metrics instrumented throughout the storage service.
journald+logrotatelogging enabled, by default, for the storage service.
- Streamlined resource management via default storage service offer filters.
- Tutorial for extending the default Universal Installer configuration in order to provide additional raw disks for the storage service to consume.
- Service bug fixes, performance fixes, as well as other doc fixes and improvements.
- Only local volume storage is currently supported.
- Automated upgrades of a running DC/OS Storage Service on an existing cluster are not yet supported.
- The service must be deployed in a DC/OS cluster running in
strictsecurity mode when configured with a service account and corresponding secret.
DC/OS Storage Service is currently in Beta and has the following known bugs.
devicesprovider plugin does not witness new or removed devices on the agent until the agent is restarted.
dcos storageCLI subcommands may fail with a gateway timeout error, but still complete successfully in the background.
- The Mesos SLRP implementation is not yet compatible with multiple profiles that consume capacity from the same provider in different ratios (for example, RAID1 and linear).
- The storage service should only list providers that it currently manages; incompletely removed providers may be incorrectly listed in some cases.
- Deleting a volume may fail with “Cannot allocate memory” on CoreOS; please use a supported version of CoreOS.
- Kernels from (including) 3.10.0-862.6.3.el7 up to (including) 3.10.0-862.11.6.el7 may panic as a result of LVM operations (https://access.redhat.com/solutions/3520511).