openstack/openstack-manuals
Code Issues Proposed changes

Merge "Renaming in HA guide"

Browse Source
This commit is contained in:
Jenkins 2013-08-29 16:13:28 +00:00 committed by Gerrit Code Review
commit b6a93932b5
8 changed files with 59 additions and 59 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/docbkx/openstack-ha/aa-controllers.txt
View File

@ -20,7 +20,7 @@ and use load-balancing and virtual IP (with HAproxy & Keepalived in this setup).
To configure our Cloud using Highly available and scalable API services, we need to ensure that:
* Using Virtual IP when configuring Keystone Endpoints.
* Using Virtual IP when configuring OpenStack Identity Endpoints.
* All OpenStack configuration files should refer to Virtual IP.
*In case of failure*

2
doc/src/docbkx/openstack-ha/aa-rabbitmq.txt
View File

@ -125,4 +125,4 @@ rabbitmqctl reset
rabbitmqctl start_app
----
Services currently working with HA queues : Nova, Cinder, Neutron, Ceilometer.
Services currently working with HA queues : OpenStack Compute, Cinder, OpenStack Networking, Ceilometer.

2
doc/src/docbkx/openstack-ha/aa-storage.txt
View File

@ -1,5 +1,5 @@
[[ha-aa-storage]]
=== Storage Backends for Glance and Cinder
=== Storage Backends for OpenStack Image and Cinder
(Coming soon)

36
doc/src/docbkx/openstack-ha/ap-glance-api.txt
View File

@ -1,17 +1,17 @@
[[s-glance-api]]
==== Highly available Glance API
==== Highly available OpenStack Image API
Glance is the Image Delivery and Registring Service in OpenStack.
Making the Glance API service highly available in active / passive mode involves
OpenStack Image is the Image Delivery and Registring Service in OpenStack.
Making the OpenStack Image API service highly available in active / passive mode involves
* configuring Glance to listen on the VIP address,
* managing Glance API daemon with the Pacemaker cluster manager,
* configuring OpenStack Image to listen on the VIP address,
* managing OpenStack Image API daemon with the Pacemaker cluster manager,
* configuring OpenStack services to use this IP address.
NOTE: Here is the http://docs.openstack.org/trunk/openstack-compute/install/apt/content/install-glance.html[documentation] for installing Glance API service.
NOTE: Here is the http://docs.openstack.org/trunk/openstack-compute/install/apt/content/install-glance.html[documentation] for installing OpenStack Image API service.
===== Adding Glance API resource to Pacemaker
===== Adding OpenStack Image API resource to Pacemaker
First of all, you need to download the resource agent to your system :
@ -22,7 +22,7 @@ chmod a+rx *
----
You may now proceed with adding the Pacemaker configuration for
Glance API resource. Connect to the Pacemaker cluster with +crm
OpenStack Image API resource. Connect to the Pacemaker cluster with +crm
configure+, and add the following cluster resources:
----
@ -31,7 +31,7 @@ include::includes/pacemaker-glance_api.crm[]
This configuration creates
* +p_glance-api+, a resource for manage Glance API service
* +p_glance-api+, a resource for manage OpenStack Image API service
+crm configure+ supports batch input, so you may copy and paste the
above into your live pacemaker configuration, and then make changes as
@ -40,20 +40,20 @@ required. For example, you may enter +edit p_ip_glance-api+ from the
virtual IP address.
Once completed, commit your configuration changes by entering +commit+
from the +crm configure+ menu. Pacemaker will then start the Glance API
from the +crm configure+ menu. Pacemaker will then start the OpenStack Image API
service, and its dependent resources, on one of your nodes.
===== Configuring Glance API service
===== Configuring OpenStack Image API service
Edit +/etc/glance/glance-api.conf+ :
----
# We have to use MySQL connection to store datas :
sql_connection=mysql://glance:password@192.168.42.101/glance
# We bind Glance API to the VIP :
# We bind OpenStack Image API to the VIP :
bind_host = 192.168.42.103
# Connect to Glance Registry service :
# Connect to OpenStack Image Registry service :
registry_host = 192.168.42.103
# We send notifications to High Available RabbitMQ :
@ -62,13 +62,13 @@ rabbit_host = 192.168.42.102
----
===== Configuring OpenStack Services to use High Available Glance API
===== Configuring OpenStack Services to use High Available OpenStack Image API
Your OpenStack services must now point their Glance API configuration to
Your OpenStack services must now point their OpenStack Image API configuration to
the highly available, virtual cluster IP address -- rather than a
Glance API server's physical IP address as you normally would.
OpenStack Image API server's physical IP address as you normally would.
For Nova, for example, if your Glance API service IP address is
For OpenStack Compute, for example, if your OpenStack Image API service IP address is
192.168.42.104 as in the configuration explained here, you would use
the following line in your +nova.conf+ file :
@ -76,7 +76,7 @@ the following line in your +nova.conf+ file :
glance_api_servers = 192.168.42.103
----
You need also to create the Glance API Endpoint with this IP.
You need also to create the OpenStack Image API Endpoint with this IP.
NOTE : If you are using both private and public IP, you should create two Virtual IP and define your endpoint like this :
----

34
doc/src/docbkx/openstack-ha/ap-keystone.txt
View File

@ -1,17 +1,17 @@
[[s-keystone]]
==== Highly available Keystone
==== Highly available OpenStack Identity
Keystone is the Identity Service in OpenStack and used by many services.
Making the Keystone service highly available in active / passive mode involves
OpenStack Identity is the Identity Service in OpenStack and used by many services.
Making the OpenStack Identity service highly available in active / passive mode involves
* configuring Keystone to listen on the VIP address,
* managing Keystone daemon with the Pacemaker cluster manager,
* configuring OpenStack Identity to listen on the VIP address,
* managing OpenStack Identity daemon with the Pacemaker cluster manager,
* configuring OpenStack services to use this IP address.
NOTE: Here is the http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ch_installing-openstack-identity-service.html[documentation] for installing Keystone service.
NOTE: Here is the http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ch_installing-openstack-identity-service.html[documentation] for installing OpenStack Identity service.
===== Adding Keystone resource to Pacemaker
===== Adding OpenStack Identity resource to Pacemaker
First of all, you need to download the resource agent to your system :
@ -24,14 +24,14 @@ chmod a+rx *
----
You may now proceed with adding the Pacemaker configuration for
Keystone resource. Connect to the Pacemaker cluster with +crm
OpenStack Identity resource. Connect to the Pacemaker cluster with +crm
configure+, and add the following cluster resources:
----
include::includes/pacemaker-keystone.crm[]
----
This configuration creates +p_keystone+, a resource for manage Keystone service.
This configuration creates +p_keystone+, a resource for manage OpenStack Identity service.
+crm configure+ supports batch input, so you may copy and paste the
above into your live pacemaker configuration, and then make changes as
@ -40,12 +40,12 @@ required. For example, you may enter +edit p_ip_keystone+ from the
virtual IP address.
Once completed, commit your configuration changes by entering +commit+
from the +crm configure+ menu. Pacemaker will then start the Keystone
from the +crm configure+ menu. Pacemaker will then start the OpenStack Identity
service, and its dependent resources, on one of your nodes.
===== Configuring Keystone service
===== Configuring OpenStack Identity service
You need to edit your Keystone configuration file (+keystone.conf+) and change the bind parameter :
You need to edit your OpenStack Identity configuration file (+keystone.conf+) and change the bind parameter :
----
bind_host = 192.168.42.103
----
@ -61,13 +61,13 @@ driver = keystone.identity.backends.sql.Identity
----
===== Configuring OpenStack Services to use High Available Keystone
===== Configuring OpenStack Services to use High Available OpenStack Identity
Your OpenStack services must now point their Keystone configuration to
Your OpenStack services must now point their OpenStack Identity configuration to
the highly available, virtual cluster IP address -- rather than a
Keystone server's physical IP address as you normally would.
OpenStack Identity server's physical IP address as you normally would.
For example with Nova, if your Keystone service IP address is
For example with OpenStack Compute, if your OpenStack Identity service IP address is
192.168.42.103 as in the configuration explained here, you would use
the following line in your API configuration file
(+api-paste.ini+):
@ -76,7 +76,7 @@ the following line in your API configuration file
auth_host = 192.168.42.103
----
You need also to create the Keystone Endpoint with this IP.
You need also to create the OpenStack Identity Endpoint with this IP.
NOTE : If you are using both private and public IP, you should create two Virtual IP and define your endpoint like this :
----

4
doc/src/docbkx/openstack-ha/ap-mysql.txt
View File

@ -160,9 +160,9 @@ Your OpenStack services must now point their MySQL configuration to
the highly available, virtual cluster IP address -- rather than a
MySQL server's physical IP address as you normally would.
For Glance, for example, if your MySQL service IP address is
For OpenStack Image, for example, if your MySQL service IP address is
192.168.42.101 as in the configuration explained here, you would use
the following line in your Glance registry configuration file
the following line in your OpenStack Image registry configuration file
(+glance-registry.conf+):
----

34
doc/src/docbkx/openstack-ha/ap-neutron-server.txt
View File

@ -1,17 +1,17 @@
[[s-neutron-server]]
==== Highly available Quantum Server
==== Highly available OpenStack Networking Server
Quantum is the network connectivity service in OpenStack.
Making the Quantum Server service highly available in active / passive mode involves
OpenStack Networking is the network connectivity service in OpenStack.
Making the OpenStack Networking Server service highly available in active / passive mode involves
* configuring Quantum to listen on the VIP address,
* managing Quantum API Server daemon with the Pacemaker cluster manager,
* configuring OpenStack Networking to listen on the VIP address,
* managing OpenStack Networking API Server daemon with the Pacemaker cluster manager,
* configuring OpenStack services to use this IP address.
NOTE: Here is the http://docs.openstack.org/trunk/openstack-network/admin/content/index.html[documentation] for installing Quantum service.
NOTE: Here is the http://docs.openstack.org/trunk/openstack-network/admin/content/index.html[documentation] for installing OpenStack Networking service.
===== Adding Quantum Server resource to Pacemaker
===== Adding OpenStack Networking Server resource to Pacemaker
First of all, you need to download the resource agent to your system :
----
@ -21,13 +21,13 @@ chmod a+rx *
----
You may now proceed with adding the Pacemaker configuration for
Quantum Server resource. Connect to the Pacemaker cluster with +crm
OpenStack Networking Server resource. Connect to the Pacemaker cluster with +crm
configure+, and add the following cluster resources:
----
include::includes/pacemaker-neutron_server.crm[]
----
This configuration creates +p_neutron-server+, a resource for manage Quantum Server service
This configuration creates +p_neutron-server+, a resource for manage OpenStack Networking Server service
+crm configure+ supports batch input, so you may copy and paste the
above into your live pacemaker configuration, and then make changes as
@ -36,10 +36,10 @@ required. For example, you may enter +edit p_neutron-server+ from the
virtual IP address.
Once completed, commit your configuration changes by entering +commit+
from the +crm configure+ menu. Pacemaker will then start the Quantum API
from the +crm configure+ menu. Pacemaker will then start the OpenStack Networking API
service, and its dependent resources, on one of your nodes.
===== Configuring Quantum Server
===== Configuring OpenStack Networking Server
Edit +/etc/neutron/neutron.conf+ :
----
@ -49,7 +49,7 @@ bind_host = 192.168.42.103
# We have to use MySQL connection to store datas :
sql_connection = mysql://neutron:password@192.168.42.101/neutron
# We bind Quantum Server to the VIP :
# We bind OpenStack Networking Server to the VIP :
bind_host = 192.168.42.103
# We send notifications to Highly available RabbitMQ :
@ -58,18 +58,18 @@ rabbit_host = 192.168.42.102
----
===== Configuring OpenStack Services to use Highly available Quantum Server
===== Configuring OpenStack Services to use Highly available OpenStack Networking Server
Your OpenStack services must now point their Quantum Server configuration to
Your OpenStack services must now point their OpenStack Networking Server configuration to
the highly available, virtual cluster IP address -- rather than a
Quantum server's physical IP address as you normally would.
OpenStack Networking server's physical IP address as you normally would.
For example, you should configure Nova for using Highly Available Quantum Server in editing +nova.conf+ file :
For example, you should configure OpenStack Compute for using Highly Available OpenStack Networking Server in editing +nova.conf+ file :
----
neutron_url = http://192.168.42.103:9696
----
You need to create the Quantum Server Endpoint with this IP.
You need to create the OpenStack Networking Server Endpoint with this IP.
NOTE : If you are using both private and public IP, you should create two Virtual IP and define your endpoint like this :
----

4
doc/src/docbkx/openstack-ha/ap-rabbitmq.txt
View File

@ -150,9 +150,9 @@ Your OpenStack services must now point their RabbitMQ configuration to
the highly available, virtual cluster IP address -- rather than a
RabbitMQ server's physical IP address as you normally would.
For Glance, for example, if your RabbitMQ service IP address is
For OpenStack Image, for example, if your RabbitMQ service IP address is
192.168.42.100 as in the configuration explained here, you would use
the following line in your Glance API configuration file
the following line in your OpenStack Image API configuration file
(+glance-api.conf+):
----