4 Commits

Author SHA1 Message Date
MaoyangLiu
8fc5ef9560 fix 'an unique' to 'a unique'
Change-Id: I1a0aaa6b76acd43e90c539cc324291dd6d729359
2018-11-24 11:19:59 +08:00
ZhongShengping
1f717c9065 Update URLs in documents according to document migration
Change-Id: Iec0908b8a4db3faa9dc4bf40082f0f898e8b779b
2017-07-14 14:08:15 +08:00
Andy McCrae
9578aa5fd7 Ensure storage/replication_ip are uniform
We need to ensure the swift services are listening on the same IP and
port as the ring is setup for. Currently we calculate these values in
different ways, which leads to the possibility that the ring is setup
for ports and IPs that the services are not listening on.

This change ensures this by calculating the storage and replication
addresses within the role - whilst still accepting overrides from
outside the role. This ensures functionality does not change, but that
it is now not possible for the swift services to not listen on the
ports/IPs defined in the ring.

As part of this change we move to set "swift_dedicated_replication"
based on whether the storage and replication addresses are the same,
rather than the specified network. This means you can run a dedicated
replication config by configuring the services, which was possible to
configure, but again would have meant the services and ring were not
configured in the same way. This is required to ensure uniformity.

Finally - we remove the ability to set a storage_port or repl_port
within the swift_vars, this was a setting that would never work in it's
current implementation. The storage/repl_port would depend entirely on
which swift service was in use, and can not be set in such a blanket
fashion. Since this was a completely not working funcitonality it has
now been removed.

Change-Id: Ibe5330cdca7fd81f379b80dc55ad06529ce4d580
2016-09-26 11:23:15 +01:00
Travis Truman
d3305e4be0 Relocate Swift configuration docs to os_swift role
Change-Id: Ic3e6540556eeb0518d8e6c59b32f38a427071799
2016-08-15 12:54:04 -04:00