crush/CrushCompiler: make current set of tunables 'safe'

We can reenable this error the next time we add new tunables.

Signed-off-by: Sage Weil <sage@inktank.com>

diff --git a/src/crush/CrushCompiler.cc b/src/crush/CrushCompiler.cc
index 43ff2b1e8af689d0e8797706772791620369cc83..b8038ca8bdb06fe1bbb19049f605f4d8e8f7dfab 100644 (file)
--- a/src/crush/CrushCompiler.cc
+++ b/src/crush/CrushCompiler.cc
@@ -348,10 +348,16 @@ int CrushCompiler::parse_tunable(iter_t const& i)
     return -1;
   }
 
+  /*
+
+    current crop of tunables are all now "safe".  reenable this when we
+    add new ones that are ... new.
+
   if (!unsafe_tunables) {
     err << "tunables are NOT FULLY IMPLEMENTED; enable with --enable-unsafe-tunables to enable this feature" << std::endl;
     return -1;
   }
+  */
 
   if (verbose) err << "tunable " << name << " " << val << std::endl;
   return 0;