mgr/cephadm: Use a persistent volume to store Loki DB#60815
mgr/cephadm: Use a persistent volume to store Loki DB#60815
Conversation
a5bc745 to
8ab1948
Compare
|
jenkins test make check arm64 |
phlogistonjohn
left a comment
There was a problem hiding this comment.
This should probably be scoped as mgr/cephadm not mgr/dashboard as dashboard is not touched by this change.
Second question: this volume mapping will tie this instance of loki to the particular host is it running on. Is this ok, if so I'd like to see that explained in comments (and commit message). Only resources that are meant to be tied to a single host or only semi-persistent (caches) ought to be volume mapped into the containers.
phlogistonjohn
left a comment
There was a problem hiding this comment.
Setting 'Request changes' in order to ensure we discuss the above comment before this is considered mergable.
|
Failures:
Overall, can't cause the two PRs that caused the direct failures mentioned or nfs module PRs. Other changes should be okay. |
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
|
|
jenkins test dashboard cephadm |
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
Current Behavior: The Loki configuration directs all data to /tmp/loki, which is not mounted as a persistent volume. This results in data being stored in a temporary location that gets cleared upon container restart. Expected Behavior: Loki data should be stored in /loki, which is backed by the persistent volume mapped to /var/lib/ceph/<fsid>/loki.<id>/data, ensuring data persistence across container restarts. Fixes: https://tracker.ceph.com/issues/69029 Signed-off-by: Aashish Sharma <aasharma@redhat.com>
8ab1948 to
70f8bdb
Compare
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
|
okay run for merging outside of anything SMB related |
adk3798
left a comment
There was a problem hiding this comment.
don't know much about this, but the PR looks like it's doing what's described
Current Behavior: The Loki configuration directs all data to /tmp/loki, which is not mounted as a persistent volume. This results in data being stored in a temporary location that gets cleared upon container restart.
Expected Behavior: Loki data should be stored in /loki, which is backed by the persistent volume mapped to /var/lib/ceph//loki./data, ensuring data persistence across container restarts.
Fixes: https://tracker.ceph.com/issues/69029
Signed-off-by: Aashish Sharma aasharma@redhat.com
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e