Add links to backfill related tracker items.

Signed-off-by: Loic Dachary <loic@dachary.org>

diff --git a/doc/dev/osd_internals/erasure_coding.rst b/doc/dev/osd_internals/erasure_coding.rst
index f9c34671569f8bb1d07484c3b9babf28a61da90e..f81453d68254444e0d83ef4e08c44c6659e0c035 100644 (file)
--- a/doc/dev/osd_internals/erasure_coding.rst
+++ b/doc/dev/osd_internals/erasure_coding.rst
@@ -278,7 +278,7 @@ PGBackend interfaces:
 - recoverable()
 - recover_object()
 
-Backfill
+`Backfill <http://tracker.ceph.com/issues/5856>`_
 --------
 
 For the most part, backfill itself should behave similarly between
@@ -292,14 +292,17 @@ replicated and erasure coded pools with a few exceptions:
    temporary pg chunk for that acting set slot.
 
 For 2, we don't really need to place the backfill peer in the acting
-set for replicated PGs anyway.  For 1, PGBackend::choose_backfill()
-should determine which osds are backfilled in a particular interval.
+set for replicated PGs anyway.
+For 1, PGBackend::choose_backfill() should determine which osds are
+backfilled in a particular interval.
 
 Core changes:
 
-- Backfill should be capable of handling multiple backfill peers
-  concurrently even for replicated pgs (easier to test for now)
-- Backfill peers should not be placed in the acting set.
+- Backfill should be capable of `handling multiple backfill peers
+  concurrently <http://tracker.ceph.com/issues/5858>`_ even for
+  replicated pgs (easier to test for now)
+- `Backfill peers should not be placed in the acting set
+  <http://tracker.ceph.com/issues/5855>`_.
 
 PGBackend interfaces: