Bug 1483096
Summary: | [RFE] colocated containerized daemons should reserve system resources | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Andrew Schoen <aschoen> |
Component: | Ceph-Ansible | Assignee: | Sébastien Han <shan> |
Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
Severity: | urgent | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | urgent | ||
Version: | 3.0 | CC: | adeza, aschoen, ceph-eng-bugs, ceph-qe-bugs, dang, flucifre, gmeno, hchen, hnallurv, jim.curtis, kdreyer, nthomas, pprakash, sankarshan, seb, shan |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | 3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-ansible-3.0.0-0.1.rc7.el7cp Ubuntu: ceph-ansible_3.0.0~rc7-2redhat1 | Doc Type: | Enhancement |
Doc Text: |
.Colocation of containerized Ceph daemons
With this release, you can colocate specific containerized Ceph daemons with OSD daemons on the same node. This approach significantly improves total cost of ownership (TCO) at small scale, reduces the minimum configuration from six nodes to three, makes upgrading more convenient, and provides better resource isolation. Also, each daemon has system resources reserved to avoid the "noisy neighbor" effect.
For details, see the link:https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/container_guide/#colocation-of-containerized-ceph-daemons[Colocation of Containerized Ceph Daemons] chapter in the Container Guide for Red Hat Ceph Storage 3.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-05 23:18:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1494421 |
Description
Andrew Schoen
2017-08-18 18:12:30 UTC
this was incorrectly assigned to 3.1, fixed. Looks good, I just added a small change. Thanks, Bara. How to verify? 1. Make sure the "docker run" command as the right flags 2. Run the tests mentioned above inside the container If 2. fails this is most likely an issue with the Docker engine. Hi, Verified that docker run command is accompanied with right set of flags. Moving to VERIFIED state based on e-mail conversation with Sebastien and Harish. Thanks. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3388 |