MLIA-825 Make backend installation more generic

Use the backend registry to manage installation routines for different
backends as well. This makes the process more generic and allows us
to move towards plug & play for backends (i.e. there should be no code
changes needed in the general MLIA code to add/support new backends).

Change-Id: Ib7c772ec52b2f4d857c2c9871e44dfff97e9d970

1 files changed, 9 insertions, 2 deletions

diff --git a/src/mlia/backend/corstone/__init__.py b/src/mlia/backend/corstone/__init__.py
index 5aa688b..7575ceb 100644
--- a/src/mlia/backend/corstone/__init__.py
+++ b/src/mlia/backend/corstone/__init__.py
@@ -4,19 +4,26 @@
 from mlia.backend.config import BackendConfiguration
 from mlia.backend.config import BackendType
 from mlia.backend.config import System
+from mlia.backend.corstone.install import get_corstone_300_installation
+from mlia.backend.corstone.install import get_corstone_310_installation
 from mlia.backend.registry import registry
 from mlia.core.common import AdviceCategory
 
 # List of mutually exclusive Corstone backends ordered by priority
-CORSTONE_PRIORITY = ("Corstone-310", "Corstone-300")
+CORSTONE_PRIORITY = {
+    "Corstone-310": get_corstone_310_installation(),
+    "Corstone-300": get_corstone_300_installation(),
+}
 
-for corstone_name in CORSTONE_PRIORITY:
+
+for corstone_name, installation in CORSTONE_PRIORITY.items():
     registry.register(
         corstone_name.lower(),
         BackendConfiguration(
             supported_advice=[AdviceCategory.PERFORMANCE, AdviceCategory.OPTIMIZATION],
             supported_systems=[System.LINUX_AMD64],
             backend_type=BackendType.CUSTOM,
+            installation=installation,
         ),
         pretty_name=corstone_name,
     )