-
Notifications
You must be signed in to change notification settings - Fork 260
/
colocating-services.xml
39 lines (38 loc) · 1.94 KB
/
colocating-services.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
<?xml version="1.0" encoding="UTF-8"?>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="co-locating-services">
<?dbhtml stop-chunking?>
<title>Co-locating services</title>
<para>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.
</para>
<para>
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:
<itemizedlist>
<listitem><para>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.</para></listitem>
<listitem><para>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.
</para></listitem>
<listitem><para>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.</para></listitem>
<listitem><para>Ensure the ports you are running the services on don't
conflict. Most ports used by OpenStack are configurable.</para></listitem>
</itemizedlist>
</para>
</section>