diff --git a/core/dbobject.class.php b/core/dbobject.class.php
index 2cc199b25..68adf3495 100644
--- a/core/dbobject.class.php
+++ b/core/dbobject.class.php
@@ -3817,7 +3817,7 @@ abstract class DBObject implements iDisplay
 	}
 
      /**
-     * @internal
+     * @overwritable-hook You can extend this method in order to provide your own logic.
      *
      * @return array
      *
diff --git a/datamodels/2.x/itop-bridge-virtualization-storage/model.itop-bridge-virtualization-storage.php b/datamodels/2.x/itop-bridge-virtualization-storage/model.itop-bridge-virtualization-storage.php
new file mode 100644
index 000000000..8864b398f
--- /dev/null
+++ b/datamodels/2.x/itop-bridge-virtualization-storage/model.itop-bridge-virtualization-storage.php
@@ -0,0 +1,18 @@
+<?php
+/**
+ * @copyright   Copyright (C) 2010-2021 Combodo SARL
+ * @license     http://opensource.org/licenses/AGPL-3.0
+ */
+
+// WARNING - WARNING - WARNING
+// DO NOT EDIT THIS FILE (unless you know what you are doing)
+//
+// If you provide a datamodel.xxxx.xml file with your module,
+// this file WILL BE overwritten by the compilation of the
+// module (during the setup) if the datamodel.xxxx.xml file
+// contains the definition of new classes or menus.
+//
+// The recommended way to define new classes (for iTop 2.0 and later) is via the XML definition.
+// This file remains in the module's template only for the cases where there is:
+// - either no new class or menu defined in the XML file
+// - or no XML file at all supplied by the module
\ No newline at end of file