OpenStack Networking is the network connectivity service in OpenStack. Making the OpenStack Networking Server service highly available in active / passive mode involves the following tasks: Configure OpenStack Networking to listen on the virtual IP address, Manage the OpenStack Networking API Server daemon with the Pacemaker cluster manager, Configure OpenStack services to use the virtual IP address. Here is the documentation for installing OpenStack Networking service.

First of all, you need to download the resource agent to your system: # cd /usr/lib/ocf/resource.d/openstack # wget https://raw.github.com/madkiss/openstack-resource-agents/master/ocf/neutron-server # chmod a+rx * You can now add the Pacemaker configuration for OpenStack Networking Server resource. Connect to the Pacemaker cluster with crm configure, and add the following cluster resources: primitive p_neutron-server ocf:openstack:neutron-server \ params os_password="secret" 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" 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 required. For example, you may enter edit p_neutron-server from the crm configure menu and edit the resource to match your preferred virtual IP address. Once completed, commit your configuration changes by entering commit from the crm configure menu. Pacemaker will then start the OpenStack Networking API service, and its dependent resources, on one of your nodes.

Edit /etc/neutron/neutron.conf: # 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

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. 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 OpenStack Networking server endpoint with this IP. If you are using both private and public IP addresses, you should create two Virtual IP addresses and define your endpoint like this: $ 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/'