Ceph : Issueshttps://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2020-07-23T15:16:56ZCeph
Redmine Dashboard - Backport #46693 (Resolved): octopus: mgr/dashboard: Don't have two different unit tes...https://tracker.ceph.com/issues/466932020-07-23T15:16:56ZStephan Müller
<p><a class="external" href="https://github.com/ceph/ceph/pull/36267">https://github.com/ceph/ceph/pull/36267</a></p> Orchestrator - Documentation #46377 (Resolved): cephadm: Missing 'service_id' in last example in ...https://tracker.ceph.com/issues/463772020-07-06T15:33:59ZStephan Müller
<p>Missing 'service_id' in last example in orchestrator#service-specification. Example can be found right above <a class="external" href="https://docs.ceph.com/docs/master/mgr/orchestrator/#placement-specification">https://docs.ceph.com/docs/master/mgr/orchestrator/#placement-specification</a> and it should look like specified in <a class="external" href="https://docs.ceph.com/docs/master/cephadm/drivegroups/#osd-service-specification">https://docs.ceph.com/docs/master/cephadm/drivegroups/#osd-service-specification</a> .</p> Ceph - Documentation #45874 (Fix Under Review): doc: Extend resolving conflict section in "Submit...https://tracker.ceph.com/issues/458742020-06-04T08:09:20ZStephan Müller
<p>Currently it's not clear how to easily continue with the backport script when a conflict is encountered.</p> Dashboard - Documentation #42350 (New): mgr/dashboard: The reason to testhttps://tracker.ceph.com/issues/423502019-10-17T12:33:33ZStephan Müller
<p>Give an interesting introduction into our tests.</p>
<p>This task should be split in the following subtasks</p>
<p>1. Describe the benefits of the different tests.</p>
<p>2. Describe consideration that are to be made to decide where I use the one or the other.</p>
<p>3. Show the benefits of different testing strategies (Test first / TDD)</p>
<p>4. Add some best practice links and showcase good tests in our code base.</p>
<p>The benefit of this should be that everybody should be capable of writing tests with the different test scopes in mind.</p> Dashboard - Documentation #41396 (Resolved): mgr/dashboard: Add a dashboard specific endpoint whi...https://tracker.ceph.com/issues/413962019-08-22T15:09:47ZStephan Müller
<p>Currently there is no defined way how to create a dashboard specific endpoint that consumes existing endpoints.</p> Dashboard - Backport #40982 (Resolved): nautilus: mgr/dashboard: Fix the table mouseenter event h...https://tracker.ceph.com/issues/409822019-07-26T13:04:35ZStephan Müller
<p><a class="external" href="https://github.com/ceph/ceph/pull/29354">https://github.com/ceph/ceph/pull/29354</a></p> Dashboard - Backport #40699 (Resolved): nautilus: mgr/dashboard: Silence Alertmanager alertshttps://tracker.ceph.com/issues/406992019-07-09T10:57:04ZStephan Müller
<p><a class="external" href="https://github.com/ceph/ceph/pull/28968">https://github.com/ceph/ceph/pull/28968</a></p> Dashboard - Backport #39534 (Resolved): nautilus: mgr/dashboard: New RBD snapshot names should be...https://tracker.ceph.com/issues/395342019-04-30T10:38:01ZStephan Müller
<p><a class="external" href="https://github.com/ceph/ceph/pull/27890">https://github.com/ceph/ceph/pull/27890</a></p> Dashboard - Backport #39371 (Resolved): nautilus: mgr/dashboard: Localization for date picker modulehttps://tracker.ceph.com/issues/393712019-04-18T09:17:43ZStephan Müller
<p><a class="external" href="https://github.com/ceph/ceph/pull/27673">https://github.com/ceph/ceph/pull/27673</a></p> Dashboard - Backport #39370 (Resolved): nautilus: mgr/dashboard: Buggy data table search fieldhttps://tracker.ceph.com/issues/393702019-04-18T09:01:40ZStephan Müller
<p><a class="external" href="https://github.com/ceph/ceph/pull/27672">https://github.com/ceph/ceph/pull/27672</a></p> Dashboard - Backport #39058 (Resolved): nautilus: mgr/dashboard: Back button componenthttps://tracker.ceph.com/issues/390582019-04-01T10:42:53ZStephan Müller
<p><a class="external" href="https://github.com/ceph/ceph/pull/27405">https://github.com/ceph/ceph/pull/27405</a></p> Dashboard - Documentation #37468 (Resolved): mgr/dashboard: Document custom RESTController endpo...https://tracker.ceph.com/issues/374682018-11-29T12:30:21ZStephan Müller
<p>Extend HACKING.rst by the fact how to extend a RESTController with a custom endpoint which has all permissions preserved.</p> Dashboard - Tasks #25162 (New): API interceptor should handle client and server side offline statushttps://tracker.ceph.com/issues/251622018-07-30T14:25:02ZStephan Müller
<p>API interceptor should handle client and server side offline status</p> mgr - Tasks #25157 (New): Refine the details of the Ceph pools opticallyhttps://tracker.ceph.com/issues/251572018-07-30T14:04:23ZStephan Müller
<p>The details of the Ceph pools in the listing are relatively raw displayed. This should be enhanced and the details should be refined optically.</p>
<a name="Data-Table"></a>
<h2 >Data Table<a href="#Data-Table" class="wiki-anchor">¶</a></h2>
<ul>
<li>Replica size is only valid for replicated pools.</li>
<li>The "type" defines, which column is valid.</li>
<li>The minimum number of replicas is missing. Maybe even as an optional column.</li>
<li>Show the pool quota.</li>
</ul>
<a name="Details"></a>
<h2 >Details<a href="#Details" class="wiki-anchor">¶</a></h2>
<ul>
<li>Show Replica size only for replicated pools.</li>
<li>Only show erasure code profile on erasure coded pools.</li>
<li>Add a mouse over or hyper link for the properties.</li>
</ul> Dashboard - Tasks #24460 (Resolved): Make notification and tasks look more human readablehttps://tracker.ceph.com/issues/244602018-06-08T15:05:20ZStephan Müller
<p>Currently the notification and tasks don't look alike and are not the nicest way to present information as it is often pretty redundant.</p>
<p>The idea is the following have 3 kinds of message types.</p>
<p>1. One runn*ing* message<br /><pre>
Creating ....
</pre></p>
<p>2. One finish*ed* message<br /><pre>
Created ...
</pre></p>
<p>3. One *fail*ure message with description<br /><pre>
Creation ... failed
error description
</pre></p>
<p>Currently our messages look like this:<br /><pre>
Create ...
description message for running/finished and failure
</pre></p>