Update installation and deployment guides (#6)

* Add gitignore and remove vs from repo

* Update Installation Guide

* Reverting back to the original deployment guide

* Clean up the last images

* Installation+Deployment Merge 1

* Updates to Client Agents Section

* Additional Edits to the Management Console Page

* Minor formatting and text edits for installation and deployment

* text change for Deployment -- version number

* Remove section numbers and update App Store images

* Reorder deploy sections

.vs/VSWorkspaceState.json

@@ -1,6 +1,9 @@
 {
   "ExpandedNodes": [
-    ""
+    "",
+    "\\install",
+    "\\install\\source"
   ],
+  "SelectedNode": "\\install\\source\\chapter05.rst",
   "PreviewInSolutionExplorer": false
 }

deploy/source/chapter02.rst

@@ -1,177 +1,38 @@
-==============================
-Deployment
-==============================
-
-Deployment Options
+Infrastructure Components
 -----------------------------
 
-As documented above, CentreStack has three logical components, the database, the worker node and the storage. This section will go through
-different deployment options. 
-
-All-In-One Deployment
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-This is the simplest deployment. The database , the worker nodes are all on the same machine as
-the storage.
-When you are serving < 1000 users or you are doing Proof-of-Concept (POC), this is the ideal deployment because of its simplicity.
-You can have the CentreStack installer install the SQL Express/MySQL on the same machine before installing CentreStack software and then pointing the database to localhost\\SQLEXPRESS or local MySQL.
-In the All-In-One deployment, the storage location is typically set to a folder on local C: drive or local D: drive.
-
-The installer can install SQL EXPRESS so it is a one-click installation for convenience.
-No need to do a separate SQL EXPRESS installation.
-
-.. Note::
-
-  If this is the first time you are installing CentreStack, this is the recommended setup because it is the easiest to setup and only takes 15-30 minutes on a clean machine. The installer will take care of all the installation without other manual steps.
-
-.. image:: _static/image003.png
-
-In the latest CentreStack installer, the installer is capable of doing the all-in-one installation without asking you to setup database separately.
-
-Single-Server Deployment
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-This is another simple deployment. It is very similar to the All-In-One deployment. The only difference is that the file storage is off the machine instead of on the machine.
-
-The external file storage can be file storage on a UNC path or it can also be an object storage service.
-
-In this deployment, the database and the Worker Node/Web Node are still deployed on the same machine.
-
-.. image:: _static/image004.png
-
-Two-Server Deployment
-^^^^^^^^^^^^^^^^^^^^^^^
-
-In the two server deployment, the database is installed in its own server;
-away from the CentreStack worker node.
-Usually, this is an intermediate step leading to the “Three-Server Deployment” and a step towards scaling up the server farm.
-
-.. image:: _static/image005.png
-
-Three-Server Deployment for Redundancy
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The 3-machine deployment is another simple deployment. The database node is installed separately.
-Two CentreStack worker nodes are installed. The “External URL” field for each node is the same,
-such as “cloud.acme.com”. The load balancer will do a round robin load balancing to either node.
-A variation of the deployment is to set “External URL” field differently for the two worker nodes.
-When “External URL” field is the same as the load balancer URL, everything is round robin.
-When “External URL” is different, such as node1.acme.com and node2.acme.com,
-the users will have affinity to one of the node.
-For example, if user1 is assigned to node1.acme.com, he will continue to use node1.acme.com.
-In this deployment, the size of the cluster is supporting 2000 concurrent-users per node.
-The benefit is that if one node is down, there is another node for redundancy.
-
-.. image:: _static/image006.jpg
-
-Multiple-Machine Deployment for Scalability
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-In this deployment, you will have clear separation of database , storage service, and the
-worker nodes in a farm of servers. 
-
-The database  is not a CentreStack worker node; it is just a server that runs SQL Server or MySQL.
-
-The worker nodes are all CentreStack nodes which run the same software.
-Most of the time, in the multiple-machine deployment, a hardware load balancer is used to distribute the load evenly.
-
-.. image:: _static/image007.png
-
-Inside a worker node, there is further division of work between a 'web node' and the rest 'worker node'.
-
-The web  nodes are used for user login. After login, the user will be re-directed to the corresponding worker node.
-(The web  node can be omitted if you have an existing Load Balancer).
-
-For the load balancing to work, all the worker nodes have to be on the same DNS domain and same level of sub domain
-(for example, they can be covered by same SSL wildcard certificate, such a \*.acme.com).  The load balancing requires at least two worker nodes.
-
-*	Install the CentreStack server on the first worker node machine. Reboot and setup the cluster admin account.
-
-*	Install the CentreStack server on all the other work nodes.
+There are three different infrastructure components (logical components that can co-exist in the same server).
+In the smallest deployment unit, the different components can co-exist in one single machine (all-in-one deployment).
 
-  On the database configuration window, use the same database server as the first installation.
 
-.. note::
+1. Worker Node Component
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-  We recommend you setup and configure the first node and make sure it runs smoothly first, before you setup and install the second node.
+      Worker node contains services like Web Browser Based File Manager, Storage Service Connectors, 
+      Active Directory connector and other key components. 
+      It is responsible for data related activities such as file upload and download,
+      permission, control and change notification. Since the data upload and download
+      usually go through worker node, thus it is called a "worker" for data transfer.
+
+      Additional nodes can be added as the load increases.
+
 
-*	From any worker node, login to CentreStack Cluster Manager with the cluster admin account
-
-  (the account you setup during the installation of the first worker node)
-
-  .. image:: _static/image008.jpg
-
-  Cluster manager is web browser based.
-
-  .. image:: _static/image009.png
-
-*	From the Cluster Control Panel, Go to Cluster Server Farm item, click on ‘Edit’ and define all worker nodes.
-
-  .. image:: _static/image010.png
-
-  After click the "Edit", the Edit Worker Node Dialog shows.
-
-  .. image:: _static/image011.png
-
-
-  **Node Name**
-
-        For each worker node, the **node name** has to be the machine’s NETBIOS name (hostname).
-
-  **External URL**
-
-        The **External URL** is the unique URL to access the node from public internet. For example, http://node1.acme.com, http://node2.acme.com
-
-  **Internal URL**
-
-        The **internal URL** is the internal DNS name/URL from the internet network. The internal URL 
-        in later build is hidden. No need to edit any more.
-
-
-  Please DO NOT add web nodes to the Cluster Worker Node list. Most of the time when you
-  have a multi-worker-node design, you are servicing many users, and most of the time you have your own load balancer.
-  In the case when you have your own load balancer, the web node functionality is merged into worker node. So you can have a zero-web-node
-  configuration.
-
-*	Setup DNS Load balancing for all worker nodes.
-
-    Most of the time you set up a firewall or a load balancer and point the DNS to the load balancer.
-    The load balancer will then forward to the CentreStack worker node. 
-
-.. note::
-
-  If you are using hardware load balancer, you can skip web-nodes and have an all-worker-node cluster.
-
-Typical Deployment in Enterprises
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Here is a typical deployment schema in Visio Diagram for very big deployments in large enterprises.
-In this deployment, the management functionality can be separated to internal management node (A property of worker node).
-When management functionality is separated to internal DNS names, the management web portal is internal only and thus more secure.
-
-.. image:: _static/image012.png
-
-High Availability Deployment
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-For high availability, you can prepare the high availability deployment in three different layers and make sure
-it is high availability within each layer.
-
-1. Storage
-
-If you are using Microsoft File Server Share as your storage, you can prepare it to be replicated, for example using DFS.
-
-If you are using Amazon S3 or Windows Azure Blob, by default it is redundant and high availability.
-
-2. Database
-
-You can use the Microsoft SQL Server Availability Group Clustering or Availability Group Fail Over to make database high 
-availability.
-
-3. CentreStack Worker Node
-
-You can have multiple centrestack worker nodes in a round robin load balancing setup to provide high availability.
-
-
-.. image:: _static/DrawingHA.png
+2. Database Component
+^^^^^^^^^^^^^^^^^^^^^^^^
 
+      The database contains persistent information for the system.
+      Database is a critical component for the smooth operation of the CentreStack server farm.
+      Local database with latency less than 10 milliseconds is recommended.
+
+      In order for all worker nodes be in the same server farm,
+      they need to point to the same database.
+
+
+3. Storage Component
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+    The storage component is the persistent storage location for files and folders. There are 
+    two different types of storage services. One is managed by CentreStack, such as the default
+    storage for the cluster and the default storage for tenants. The other is imported storage, 
+    for example, having existing file server network shares that aren't managed by CentreStack but can be 
+    imported into CentreStack for remote and mobile access.