From 57ade0264bc3301d9cc1f0f1e0d4a752f77e56f5 Mon Sep 17 00:00:00 2001 From: Tom Fifield Date: Mon, 12 Nov 2012 14:39:09 +0900 Subject: [PATCH] Add a section on co-locating services fixes bug 988053 As in the bug request, people are often interested in running services from different OpenStack projects on one piece of kit. This patch adds a new section in common on co-locating services, explaining the catches and things to look out for. It's then linked from the compute install guide's architecture section, and the install guide's assumption section. Change-Id: I42a2843cb69fffd523a18143dc41e5275d9e5215 --- doc/src/docbkx/common/colocating-services.xml | 39 +++++++++++++++++++ .../bk-compute-adminguide.xml | 2 +- .../computeinstall.xml | 2 + .../openstack-install/ch_assumptions.xml | 1 + 4 files changed, 43 insertions(+), 1 deletion(-) create mode 100644 doc/src/docbkx/common/colocating-services.xml diff --git a/doc/src/docbkx/common/colocating-services.xml b/doc/src/docbkx/common/colocating-services.xml new file mode 100644 index 00000000000..fe8f6913b93 --- /dev/null +++ b/doc/src/docbkx/common/colocating-services.xml @@ -0,0 +1,39 @@ + +
+ + Co-locating services + While in a best-practice deployment, each OpenStack project's services + would live on a different machine, this is not always practical. + For example, in small deployments there might be too few machines + available, or a limited number of public IP addresses. Components from + different OpenStack projects are not necessarily engineered to be able to be + co-located, however many users report success with a variety of + deployment scenarios. + + + The following is a series of pointers to be used when co-location + of services from different OpenStack projects on the same machine + is a must: + + Ensure dependencies aren't in conflict. The OpenStack + Continuous Integration team does attempt to ensure there is no + conflict - so if you see issues during package installation, + consider filing a bug. + Monitor your systems and ensure they are not overloaded. + Some parts of OpenStack use a lot of CPU time (eg Swift Proxy + Servers), while others are IO focused (eg Swift Object Server). + Try to balance these so they complement each other. + + Beware of security. Different parts of OpenStack assume + different security models. For example, Swift assumes the storage + nodes will be on a private network and does not provide additonal + security between nodes in the cluster. + Ensure the ports you are running the services on don't + conflict. Most ports used by OpenStack are configurable. + + +
+ diff --git a/doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml b/doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml index df13d99f211..308d4fa4d96 100644 --- a/doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml +++ b/doc/src/docbkx/openstack-compute-admin/bk-compute-adminguide.xml @@ -188,4 +188,4 @@ - + diff --git a/doc/src/docbkx/openstack-compute-admin/computeinstall.xml b/doc/src/docbkx/openstack-compute-admin/computeinstall.xml index 591c3aab62b..f61d0f5bb12 100644 --- a/doc/src/docbkx/openstack-compute-admin/computeinstall.xml +++ b/doc/src/docbkx/openstack-compute-admin/computeinstall.xml @@ -80,6 +80,8 @@ + +
diff --git a/doc/src/docbkx/openstack-install/ch_assumptions.xml b/doc/src/docbkx/openstack-install/ch_assumptions.xml index 6277c2f1d63..48c129c2a5f 100644 --- a/doc/src/docbkx/openstack-install/ch_assumptions.xml +++ b/doc/src/docbkx/openstack-install/ch_assumptions.xml @@ -89,4 +89,5 @@ service running in a multi-node install, though if high availability for networks is required, there are additional options. +