| Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes-Bug: #1482986
Change-Id: I72619ef18d24038b46d09e77887d6610ef6e8327
|
|
Partially-Implements: blueprint remove-config-internal
Change-Id: Ic6b7cb217a126c53c0055dbcac4d345583599eb1
|
|
The tgtd process was not being started in the cinder-volume container.
This results in iSCSI not being avialable for Cinder to operate
against. Unfortunately cinder doesn't report the problem because LVM
is responsible for the iSCSI mapping.
Co-Authored-By: Ryan Hallisey <rhallise@redhat.com>
Closes-Bug: 1473090
Closes-Bug: 1469323
Change-Id: Ie3403c5c3f81beb48960e838b4274e0c5796e387
|
|
Partially Implements: Blueprint standard-start
Change-Id: I9fa5cc8f6f57b46f8af165778388435b91c28447
|
|
The only files in the docker image directories that differ majorly between
distros are the Dockerfiles (e.g. different package manager mechanisms,
different repo sources, etc).
The supporting files such as the start.sh/check.sh and config files should
largely stay the same between base images.
This change moves these files up into a "common" directory, and symlinks them
in the same way that the build script is managed. This means when adding a new
base distro only new Dockerfiles need to be created. Also, if a distro does
happen to require a vastly different start.sh script for example, one can
choose to simply not symlink to the common and instead drop in a custom one.
Implements: blueprint refactor-base-image-layout
Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284
|
|
Cinder is going to be split up into four containers.
- cinder-api
- cinder-scheduler
- cinder-volume
- cinder-backup
Co-Authored-By: Daneyon Hansen <danehans@cisco.com>
Co-Authored-By: Ian Main <imain@redhat.com>
Implements: blueprint cinder-container
Closes-bug: #1460136
Change-Id: I688471151ffa54d547b9aa0f2f2e2ea7f68f288d
|