f82749457c
In the swarm_atomic and k8s_atomic drivers container images are stored in a dedicated cinder volume per cluster node. It is proven that this architecture can be a scalability bottleneck. Make the use of cinder volumes for container images and opt-in option. If docker-volume-size is not specified no cinder volumes will be created. Before, if docker-volume-size wasn't specified the default value was 25. To use cinder volumes for container storage the user will interact with magnum as before, (meaning the valid values are integers starting from 1). Closes-Bug: #1638006 Change-Id: I3394c62a43bbf950b7cf0b86a71b1d9b0481d68f
11 lines
410 B
YAML
11 lines
410 B
YAML
---
|
|
prelude: >
|
|
Currently, the swarm and the kubernetes drivers use
|
|
a dedicated cinder volume to store the container
|
|
images. It was been observed that one cinder volume
|
|
per node is a bottleneck for large clusters.
|
|
fixes:
|
|
- Make the dedicated cinder volume per node an opt-in
|
|
option. By default, no cinder volumes will be created
|
|
unless the user passes the docker-volume-size argument.
|