openstack-manuals/doc/config-reference/ch_computeconfigure.xml
Don Domingo a4465257c1 Added section for Compute node firewall config
Added a new section to the Config Reference on what ports to open on
each compute node (and how). Upon consultation, it seems that adding
a port config section in each component chapter is a better way to
address bug#1261617.

I'll submit follow-up patches adding a firewall configuration section
to each Config Ref Guide chapter/component if this patch gets merged.

Change-Id: Ie53e73b7cd2ec7af81f264338a4676952dd168e1
Partial-Bug: #1261617
2014-02-04 09:47:40 +10:00

107 lines
5.2 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<chapter 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="ch_configuring-openstack-compute">
<title>Compute</title>
<para>The OpenStack Compute service is a cloud computing fabric
controller, which is the main part of an IaaS system. You can use
OpenStack Compute to host and manage cloud computing systems. This
section describes the OpenStack Compute configuration
options.</para>
<para>To configure your Compute installation, you must define
configuration options in these files:</para>
<itemizedlist>
<listitem>
<para><filename>nova.conf</filename>. Contains most of the
Compute configuration options. Resides in the
<filename>/etc/nova</filename> directory.</para>
</listitem>
<listitem>
<para><filename>api-paste.ini</filename>. Defines Compute
limits. Resides in the <filename>/etc/nova</filename>
directory.</para>
</listitem>
<listitem>
<para>Related Image Service and Identity Service management
configuration files.</para>
</listitem>
</itemizedlist>
<xi:include href="compute/section_nova-conf.xml"/>
<section xml:id="configuring-logging">
<title>Configure logging</title>
<para>You can use <filename>nova.conf</filename> file to configure
where Compute logs events, the level of logging, and log
formats.</para>
<para>To customize log formats for OpenStack Compute, use these
configuration option settings.</para>
<xi:include href="../common/tables/nova-logging.xml"/>
</section>
<section xml:id="configuring-authentication-authorization">
<title>Configure authentication and authorization</title>
<para>There are different methods of authentication for the
OpenStack Compute project, including no authentication. The
preferred system is the OpenStack Identity Service, code-named
Keystone.</para>
<para>To customize authorization settings for Compute, see these
configuration settings in <filename>nova.conf</filename>.</para>
<xi:include href="../common/tables/nova-authentication.xml"/>
<para>To customize certificate authority settings for Compute, see
these configuration settings in
<filename>nova.conf</filename>.</para>
<xi:include href="../common/tables/nova-ca.xml"/>
<para>To customize Compute and the Identity service to use LDAP as
a backend, refer to these configuration settings in
<filename>nova.conf</filename>.</para>
<xi:include href="../common/tables/nova-ldap.xml"/>
</section>
<xi:include href="compute/section_compute-configure-ipv6.xml"/>
<xi:include href="compute/section_compute-configure-migrations.xml"/>
<section xml:id="configuring-resize">
<?dbhtml stop-chunking?>
<title>Configure resize</title>
<para>Resize (or Server resize) is the ability to change the
flavor of a server, thus allowing it to upscale or downscale
according to user needs. For this feature to work properly, you
might need to configure some underlying virt layers.</para>
<section xml:id="kvm-resize">
<title>KVM</title>
<para>Resize on KVM is implemented currently by transferring the
images between compute nodes over ssh. For KVM you need
hostnames to resolve properly and passwordless ssh access
between your compute hosts. Direct access from one compute
host to another is needed to copy the VM file across.</para>
<para>Cloud end users can find out how to resize a server by
reading the <link
xlink:href="http://docs.openstack.org/user-guide/content/nova_cli_resize.html"
>OpenStack End User Guide</link>.</para>
</section>
<section xml:id="xenserver-resize">
<title>XenServer</title>
<para>To get resize to work with XenServer (and XCP), you need
to establish a root trust between all hypervisor nodes and
provide an /image mount point to your hypervisors dom0.</para>
</section>
<!-- End of XenServer/Resize -->
</section>
<!-- End of configuring resize -->
<xi:include href="compute/section_compute-configure-db.xml"/>
<xi:include href="../common/section_compute_config-firewalls.xml"/>
<!-- Oslo rpc mechanism (such as, Rabbit, Qpid, ZeroMQ) -->
<xi:include href="../common/section_rpc.xml"/>
<xi:include href="../common/section_compute_config-api.xml"/>
<xi:include href="../common/section_compute-configure-ec2.xml"/>
<xi:include href="../common/section_compute-configure-quotas.xml"/>
<xi:include href="../common/section_compute-configure-console.xml"/>
<xi:include
href="compute/section_compute-configure-service-groups.xml"/>
<xi:include href="../common/section_fibrechannel.xml"/>
<xi:include href="compute/section_compute-hypervisors.xml"/>
<xi:include href="compute/section_compute-scheduler.xml"/>
<xi:include href="compute/section_compute-cells.xml"/>
<xi:include href="compute/section_compute-conductor.xml"/>
<xi:include href="compute/section_compute-security.xml"/>
<xi:include href="compute/section_compute-config-samples.xml"/>
<xi:include href="compute/section_compute-options-reference.xml"/>
</chapter>