d6af412fa7
This patch breaks the monolithic bk-ha-guide.xml file into chapters and sections. Section files are placed in subdirectories, with the subdirectories named after the chapters (and parts) to which they belong. This patch just does structural fixes. Once it's in, we can begin to do content cleanup in manageable chunks. Change-Id: I27397834141a3e6c305f60e71350ce869ab7c8a1 Implements: blueprint convert-ha-guide-to-docbook
90 lines
4.9 KiB
XML
90 lines
4.9 KiB
XML
<section xmlns="http://docbook.org/ns/docbook"
|
||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||
version="5.0" xml:id="s-neutron-server">
|
||
<info>
|
||
<title>Highly available OpenStack Networking server</title>
|
||
</info>
|
||
<simpara>OpenStack Networking is the network connectivity service in OpenStack.
|
||
Making the OpenStack Networking Server service highly available in active / passive mode involves</simpara>
|
||
<itemizedlist>
|
||
<listitem>
|
||
<simpara>
|
||
Configure OpenStack Networking to listen on the VIP address,
|
||
</simpara>
|
||
</listitem>
|
||
<listitem>
|
||
<simpara>
|
||
managing OpenStack Networking API Server daemon with the Pacemaker cluster manager,
|
||
</simpara>
|
||
</listitem>
|
||
<listitem>
|
||
<simpara>
|
||
Configure OpenStack services to use this IP address.
|
||
</simpara>
|
||
</listitem>
|
||
</itemizedlist>
|
||
<note>
|
||
<simpara>Here is the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_installing-openstack-networking.html">documentation</link> for installing OpenStack Networking service.</simpara>
|
||
</note>
|
||
<section xml:id="_add_openstack_networking_server_resource_to_pacemaker">
|
||
<info>
|
||
<title>Add OpenStack Networking Server resource to Pacemaker</title>
|
||
</info>
|
||
<simpara>First of all, you need to download the resource agent to your system:</simpara>
|
||
<screen>cd /usr/lib/ocf/resource.d/openstack
|
||
wget https://raw.github.com/madkiss/openstack-resource-agents/master/ocf/neutron-server
|
||
chmod a+rx *</screen>
|
||
<simpara>You can now add the Pacemaker configuration for
|
||
OpenStack Networking Server resource. Connect to the Pacemaker cluster with <literal>crm
|
||
configure</literal>, and add the following cluster resources:</simpara>
|
||
<screen>primitive p_neutron-server ocf:openstack:neutron-server \
|
||
params os_password="secrete" os_username="admin" os_tenant_name="admin" \
|
||
keystone_get_token_url="http://192.168.42.103:5000/v2.0/tokens" \
|
||
op monitor interval="30s" timeout="30s"</screen>
|
||
<simpara>This configuration creates <literal>p_neutron-server</literal>, a resource for manage OpenStack Networking Server service</simpara>
|
||
<simpara><literal>crm configure</literal> supports batch input, so you may copy and paste the
|
||
above into your live pacemaker configuration, and then make changes as
|
||
required. For example, you may enter <literal>edit p_neutron-server</literal> from the
|
||
<literal>crm configure</literal> menu and edit the resource to match your preferred
|
||
virtual IP address.</simpara>
|
||
<simpara>Once completed, commit your configuration changes by entering <literal>commit</literal>
|
||
from the <literal>crm configure</literal> menu. Pacemaker will then start the OpenStack Networking API
|
||
service, and its dependent resources, on one of your nodes.</simpara>
|
||
</section>
|
||
<section xml:id="_configure_openstack_networking_server">
|
||
<info>
|
||
<title>Configure OpenStack Networking server</title>
|
||
</info>
|
||
<simpara>Edit <literal>/etc/neutron/neutron.conf</literal> :</simpara>
|
||
<screen># We bind the service to the VIP:
|
||
bind_host = 192.168.42.103
|
||
|
||
# We bind OpenStack Networking Server to the VIP:
|
||
bind_host = 192.168.42.103
|
||
|
||
# We send notifications to Highly available RabbitMQ:
|
||
notifier_strategy = rabbit
|
||
rabbit_host = 192.168.42.102
|
||
|
||
[database]
|
||
# We have to use MySQL connection to store data:
|
||
connection = mysql://neutron:password@192.168.42.101/neutron</screen>
|
||
</section>
|
||
<section xml:id="_configure_openstack_services_to_use_highly_available_openstack_networking_server">
|
||
<info>
|
||
<title>Configure OpenStack services to use highly available OpenStack Networking server</title>
|
||
</info>
|
||
<simpara>Your OpenStack services must now point their OpenStack Networking Server configuration to
|
||
the highly available, virtual cluster IP address — rather than an
|
||
OpenStack Networking server’s physical IP address as you normally would.</simpara>
|
||
<simpara>For example, you should configure OpenStack Compute for using highly available OpenStack Networking server in editing <literal>nova.conf</literal> file:</simpara>
|
||
<screen>neutron_url = http://192.168.42.103:9696</screen>
|
||
<simpara>You need to create the OpenStack Networking server endpoint with this IP.</simpara>
|
||
<note>
|
||
<simpara>If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this:</simpara>
|
||
</note>
|
||
<screen>keystone endpoint-create --region $KEYSTONE_REGION --service-id $service-id --publicurl 'http://PUBLIC_VIP:9696/' --adminurl 'http://192.168.42.103:9696/' --internalurl 'http://192.168.42.103:9696/'</screen>
|
||
</section>
|
||
</section>
|