contents for OPNFV composite docs

Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>

Change-Id: I557819f8a67b8882de87c94bbca8177a89b55d6d
(cherry picked from commit 1e95ffeaac59aee8decf3ccf6721330de19f491e)

1 files changed, 49 insertions, 0 deletions

diff --git a/docs/platformoverview/platformoverview.rst b/docs/platformoverview/platformoverview.rst
new file mode 100644
index 00000000..e6ef8859
--- /dev/null
+++ b/docs/platformoverview/platformoverview.rst
@@ -0,0 +1,49 @@
+Doctor platform components and features
+=======================================
+
+..
+    This section will be compiled into OPNFV composite document.
+
+https://wiki.opnfv.org/doctor
+
+Features
+--------
+
+Doctor platform, as of Brahmaputra release, provides the two features:
+
+* Immediate Notification
+* Consistent resource state awareness (Compute/host-down)
+
+These features enable high availability of Network Services on top of
+the virtualized infrastructure. Immediate notification allows VNF managers
+(VNFM) to process recovery actions promptly once a failure has occurred.
+Consistency of resource state is necessary to properly execute recovery
+actions properly in the VIM.
+
+Components
+----------
+
+Doctor platform, as of Brahmaputra release, consists of the following
+components:
+
+* OpenStack Compute (Nova)
+* OpenStack Telemetry (Ceilometer)
+* OpenStack Alarming (Aodh)
+* Doctor Inspector
+* Doctor Monitor
+
+.. note::
+    Doctor Inspector and Monitor are sample implementation for reference.
+
+You can see an overview of the Doctor platform and how components interact in
+:numref:`figure-p1`.
+
+.. figure:: images/figure-p1.png
+    :name: figure-p1
+    :width: 100%
+
+    Doctor platform and typical sequence (Brahmaputra)
+
+Detailed information on the Doctor architecture can be found in the Doctor
+requirements documentation:
+http://artifacts.opnfv.org/doctor/docs/requirements/05-implementation.html