github.com/technosophos/deis@v1.7.1-0.20150915173815-f9005256004b/docs/_includes/_isolating-planes-description.rst (about) 1 Whether built for evaluation or to host production applications, when managing a 2 small Deis cluster (three to five nodes), it is reasonable to accept the 3 platform's default behavior wherein the Control Plane, Data Plane, and Router 4 Mesh are not isolated from one another. (See :ref:`architecture`.) This means 5 Control Plane components such as the :ref:`controller` or :ref:`database` will 6 be eligible to run on any node, as will the Router Mesh and the Data Plane 7 components such as :ref:`logspout`, :ref:`publisher`, and deployed applications. 8 9 In larger clusters however, nodes are more easily thought of as a commodity. 10 Operators may scale clusters out to meet demand or in to conserve resources. In 11 such cases, it is beneficial to isolate the Control Plane, which has no 12 significant need to scale (and optionally, the Router Mesh) to a small, fixed 13 number of nodes that are exempt from such scaling events. This eliminates the 14 possibility that Control Plane components running on a decommissioned node will 15 experience downtime as they are rescheduled. Additionally, this reserves the 16 resources of a large (and possibly dynamic) pool of nodes for the workloads that 17 are most likely to scale-- applications.