stackforge/puppet-openstack
Code Issues Proposed changes

Add Support for Splitting Proxy and Storage Networks

Browse Source 
Previously, both proxy and storage (ring) interfaces utilized
the same IP address.  This is an uncommon deployment model,
as proxy and storage/ring services are usually seperated across
multiple networks.

This change introduces the new parameter swift_proxy_net_ip that
alows users to specify a seperate ip address for binding the
Swift proxy service.  Defaults to the same address as the
swift_local_net_ip parameter ($::ipaddress_eth0) for backwards
compatibility and for proxy/storage networks to share the same ip

Change-Id: I2cc6bd9e430a93596236b2b5c8015cf32c981502
This commit is contained in:
danehans
2013-07-22 16:46:00 +00:00
parent 4b9d12e569
commit 5ee1d2389c
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
manifests/swift/proxy.pp
View File

@@ -4,6 +4,7 @@ class openstack::swift::proxy (
$swift_user_password = 'swift_pass',
$swift_hash_suffix = 'swift_secret',
$swift_local_net_ip = $::ipaddress_eth0,
$swift_proxy_net_ip = $::ipaddress_eth0,
$ring_part_power = 18,
$ring_replicas = 3,
$ring_min_part_hours = 1,
@@ -41,7 +42,7 @@ class openstack::swift::proxy (
}
class { '::swift::proxy':
proxy_local_net_ip => $swift_local_net_ip,
proxy_local_net_ip => $swift_proxy_net_ip,
pipeline => $proxy_pipeline,
port => $proxy_port,
workers => $proxy_workers,