Ceph : Issueshttps://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2020-04-28T13:11:52ZCeph
Redmine Dashboard - Feature #45306 (New): mgr/dashboard: asynchronous back-end: Use HTTP2 or websocketshttps://tracker.ceph.com/issues/453062020-04-28T13:11:52ZStephan Müller
<p>In order to determine what we want to use in future. I will compare both HTTP2 and websockets.</p>
<p>First a bunch of information.</p>
<p>Currently we use the protocol HTTP1.1, which only allows one request per connection.</p>
<p>With HTTP2 and websockets it is possible to allow an unlimited amount of request per connection.</p>
<p>What does one request per connection mean? For example a client asks the server for a file, this will open a connection telling the server GET me something, the server will respond and close the connection. As our dashboard does not only consist of one file, a lot of connections are made. To meet the demand of any modern site of so many connections all modern browsers will do 8 connections simultaneously. On every connection also the same header is send.</p>
<p>What does unlimited amount of requests per connection mean? For example a client asks for a (whole) website. The client sends the first request like in HTTP1.1, the server responds with an HTTP1.1 Upgrade header, client and server negotiate which protocol to use (handshake). A connection is established and left open for requests. The client sends requests for multiple files while the server already responds with the files. This maxes out the established connection, as both participants can send at the same time (for example a video chat). As the connection is left open the server can PUSH data to the client even if he had not explicitly asked for (removes polling). To save data, only the headers during the handshake are send, they will not be send multiple times.</p>
<p>Whats the difference between HTTP2 (released as standard 2015) and websockets (released as standard 2011)?<br />Both only need one connection. Websockets can run insecure using port 80 and both can run secure using port 443. Websockets use a different URL prefix <strong>ws://</strong> for insecure connections or <strong>wss://</strong> for secure ones, HTTP2 uses only <strong>https://</strong> as prefix. If HTTP2 is used data will automatically be compressed and the handshake is easier to implement than with websockets.</p>
<p>Sure HTTP2 is the better one as the protocol is much newer, but can we use it with cherrypy?<br />Currently I only found a <a href="https://docs.cherrypy.org/en/latest/advanced.html#websocket-support" class="external">plugin</a> for cherrypy to allow websockets.<br />I've not found one for HTTP2 yet but I'm still collecting information.</p> Dashboard - Feature #44621 (Pending Backport): mgr/dashboard: Automatic preselection of failure d...https://tracker.ceph.com/issues/446212020-03-16T12:12:19ZStephan Müller
<p>Use the automatic preselection of the crush rule creation form inside the erasure code profile form to prevent wrong configured ec profiles which can't be used in the end.</p> Dashboard - Bug #44620 (Resolved): mgr/dashboard: Pool form max sizehttps://tracker.ceph.com/issues/446202020-03-16T12:07:27ZStephan Müller
<p>Currently the pool form max size is determined by "max_size" of the selected rule or the maximum amount of available OSDs. The amount can be wrong if the failure domain of the rule is not OSD.</p>
<p>I'm also currently not sure if "max_size" and "min_size" are useful values to show, at least pools created on a vstart cluster always show the same min and max size values. Please make that sure that those values can still be used safely.</p> Dashboard - Feature #43351 (New): mgr/dashboard: [RFC] Actions assistanthttps://tracker.ceph.com/issues/433512019-12-17T10:34:10ZStephan Müller
<p>Not sure if this is needed for all pages but it could help users.</p>
<p>I just looked at the OSD page which is crowed by actions.</p>
<p>There are two ways to implement it,<br />as an modal that triggers the action modal,<br />or as an modal that describes what to do in order to trigger the action.</p>
<p>The second approach could be implemented globally and not only for a specific page as it could search through every page actions that are available.</p>
<p>How the modal should look like?<br />It should be pretty straight forward like an FAQ search.<br />If you open it you will see a big input field to type in words that describe what you want to do.</p>
<p>The string will be used to calculate a score for each available description. Than the highest ranked actions (3, 5 or 10?) will be shown, sorted by rank.</p>
<p>The action will shown as accordion showing the description of it if expanded and the button to take the action or the help text to get to the page and action.</p>
<p>As said in the beginning, I'm not sure if we need this.</p> mgr - Bug #41795 (New): mgr: Time series data of pool decreases itself when reducing the amount o...https://tracker.ceph.com/issues/417952019-09-12T14:18:54ZStephan Müller
<p>Time series data of pool decreases itself when reducing the amount of PGs of a pool.</p>
<p>Time series data should only increase, not decrease.</p>
<p>(I'm not sure if this is the right place for this bug.)</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 - Bug #40330 (Resolved): mgr/dashboard: Warning about stale data makes it hard to click...https://tracker.ceph.com/issues/403302019-06-13T12:29:53ZStephan Müller
<p>Warning about Stale data in the datatable makes the content move up and down, making it hard to hit a certain row</p> Dashboard - Feature #40296 (In Progress): mgr/dashboard: Maintain and improve code coverage on da...https://tracker.ceph.com/issues/402962019-06-12T12:46:28ZStephan Müller
<p>Find <a href="https://github.com/marketplace?utf8=%E2%9C%93&query=coverage" class="external">github plugins</a> or extend Jenkins to enforce a test coverage that cannot decrease.</p>
<p>Best would be on a per file basis for unit tests.</p>
<p>Currently no idea how to measure E2E and API tests, may be there is a way.</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 - Cleanup #38936 (New): mgr/dashboard: Unify polling behaviorhttps://tracker.ceph.com/issues/389362019-03-25T13:41:58ZStephan Müller
<p>Unify the polling behavior means that all API calls should be handled similar on failure.</p>
<p>The idea is that the dashboard can recover from connection issues automatically, but it should not send out notification on every failure after the initial or it should raise the polling time on each failure.</p>
<p>INHO muting notifications that would be triggered after the initial failure sounds like the best idea.</p> Dashboard - Tasks #37291 (Resolved): mgr/dashboard: Add a command to easily test e2e test with a ...https://tracker.ceph.com/issues/372912018-11-16T15:52:25ZStephan Müller
<p>To achieve this I currently need to run `npm run e2e -- --dev-server-target` which is a bit long and not everybody knows about this option.</p>