more doc cleanups

ucloud/docs/source/introduction.rst

@@ -23,45 +23,14 @@ different use cases:
 
 Architecture
 ------------
+We try to reuse existing components for ucloud. Generally speaking,
+ucloud consist of a variety of daemons who handle specific tasks and
+connect to a shared database.
 
+All interactions with the clients are done through an API.
 
+ucloud consists of the following components:
 
-suuuuuuubsub
-^^^^^^^^^^^^
-
-and following a
-
-para
-""""
-
-para2?
-
-para2!
-""""""
-mo moo!
-
-Introduction
-
-What is ucloud?
-~~~~~~~~~~~~~~~
-
-
-
-Tech Stack
-----------
-* Python 3 as main language.
-* Flask for APIs.
-* JSON for specifications.
-* QEMU (+ kvm acceleration) as hypervisor.
-* etcd for key/value storage (specifically all metadata e.g Virtual Machine Specifications, Networks Specifications, Images Specifications etc.).
-* CEPH for image storage.
-* uotp for user authentication.
-* netbox for IPAM.
-* radvd for Router Advertisement.
-
-
-Components
-----------
 * API
 * Scheduler
 * Host
@@ -69,26 +38,21 @@ Components
 * Image Scanner
 * Metadata Server
 * VM Init Scripts (dubbed as ucloud-init)How does ucloud work?
-=====================
-
-ucloud is separeted into 3 systems:
-
-1. The client side for using ucloud
-2. The server side
-3. The supporting infrastructure (databases, virtualisation, etc.)
 
 
-Depending on your use case, select one of the following guides to
-continue:
+Tech Stack
+----------
+The following technologies are utilised:
 
-* I want to use
-* I want to operate/run ucloud as a service
+* Python 3
+* Flask
+* QEMU as hypervisor
+* etcd (key/value store)
+* radvd for Router Advertisement
 
 
-Architecture
-------------
-Description of the ucloud architecture
+Optional components:
 
-
-Authentication
-~~~~~~~~~~~~~~
+* CEPH for distributed image storage
+* uotp for user authentication
+* netbox for IPAM