init structure for vio multi cloud

octo-technology · Jan 25, 2023 · 3aa27bc · 3aa27bc
1 parent a583cc2
commit 3aa27bc
Show file tree

Hide file tree

Showing 5 changed files with 19 additions and 6 deletions.
diff --git a/docs/images/business_rules.drawio → docs/drawio/business_rules.drawio b/docs/images/business_rules.drawio → docs/drawio/business_rules.drawio
diff --git a/...om-model-to-model-during-inference.drawio → ...om-model-to-model-during-inference.drawio b/...om-model-to-model-during-inference.drawio → ...om-model-to-model-during-inference.drawio
diff --git a/docs/drawio/vio-archi-cloud-azure.svg b/docs/drawio/vio-archi-cloud-azure.svg
diff --git a/docs/index.md b/docs/index.md
@@ -59,9 +59,3 @@ Once all services are up and running you can access:
 From the [edge interface](edge_interface.md) you can load a configuration and run the trigger button that will trigger the Orchestrator API and launch the following actions:
 
  ![vio-architecture-stack](images/edge_orchestrator-actions.png)
-
-## Implementation example
-
-Here you can find an implementation of VIO deployed on Azure (vio-hub) managing a fleet of Raspberrys (vio-edge):
-
- ![vio-architecture-stack](images/vio_azure_stack.png)
diff --git a/docs/overview.md b/docs/overview.md
@@ -31,3 +31,18 @@ Each sub folders below are indeed a module, an application, an independant micro
 - [The hub deployment playbook](hub_deployment.md)
 
 All of those modules have been packages inside a dedicated docker images to facilitate their deployment.
+
+## Cloud agnostic
+
+### VIO hub deployed on azure
+
+![vio-architecture-stack](drawio/vio-archi-cloud-azure.svg)
+
+### VIO hub deployed on GCP
+
+![vio-architecture-stack](drawio/vio-archi-cloud-azure.svg)
+
+### VIO hub deployed on AWS
+
+![vio-architecture-stack](drawio/vio-archi-cloud-azure.svg)
+