Updating xos-component image
Change-Id: Iaaff187b79930f1aebd7ad3300ea74f0983956ad
diff --git a/docs/static/xos_components.jpg b/docs/static/xos_components.jpg
new file mode 100644
index 0000000..81464a3
--- /dev/null
+++ b/docs/static/xos_components.jpg
Binary files differ
diff --git a/docs/static/xos_containers.png b/docs/static/xos_containers.png
deleted file mode 100644
index 8d86be0..0000000
--- a/docs/static/xos_containers.png
+++ /dev/null
Binary files differ
diff --git a/docs/xos_internals.md b/docs/xos_internals.md
index 951dcd2..5f80812 100644
--- a/docs/xos_internals.md
+++ b/docs/xos_internals.md
@@ -4,17 +4,20 @@
controller functionaly, including the data model, synchronizers, and northbound
APIs. The following is an inventory of those containers:
-| Name | Description | Ports |
+| Name | Description | Internal Ports |
| ---- | ----------- | ----- |
| xos-core | The core of the platform, contains the model definition and the xProto toolchain | 50051, 500515 |
| xos-db | The Postgres instance that persists the data-model | 5432 |
| xos-redis | A Redis instance, used as pub/sub channel for internal notifications | 5432 |
-| xos-tosca | Northbound TOSCA interface, accessible via REST at `/xos-tosca`| 9102|
-| xos-gui | Northbound GUI interface, accessible at `/xos`| 4000|
+| xos-tosca | Northbound TOSCA interface, accessible via REST | 9102|
+| xos-gui | Northbound GUI interface| 4000|
| xos-ws | Listens to `redis` events and propagates them over web-sockets for notifications| 3000|
| xos-chameleon | Northbound REST interface, accessible at `/xosapi/v1/..` (`swagger` is published at `/apidocs/`| 3000|
+| kafka | Event bus shared between all the CORD components that needs it | 9092|
+
+> The dotted lines identify optional components that are required only in certain configurations
All the communication between containers happen over `gRPC` except for
`xos-gui` where it is a combination of REST and web-socket.
-
+
