750ccaa9e8
We can simplify and refactor swift_rings.py and swift_rings_check.py by moving to a "FULL_HOST_KEY" model where we simply compare the full string, rather than individual elements. To do this we need to adjust the contents template to use the same field values as used by swift: * rename repl_ip to replication_ip * rename repl_port to replication_port Additionally, this allows us the ability to change port values on the fly, by adjusting the "DEVICE_KEY" to only be the IP and device name the port will now automatically get changed if the service port changes. This is a precursor to adjusting the default swift storage service ports to match upstream defaults, and will reduce the upgrade impact of that task. Change-Id: I704edcba4facb2170990ebec2a67d4179a023fc2
12 lines
490 B
YAML
12 lines
490 B
YAML
---
|
|
features:
|
|
- Change the port for devices in the ring by adjusting
|
|
the port value for services, hosts, or devices. This
|
|
will not involve a rebalance of the ring.
|
|
- Changing the port for a device, or group of devices,
|
|
carries a brief period of downtime to the swift
|
|
storage services for those devices. The devices will
|
|
be unavailable during period between when the
|
|
storage service restarts after the port update, and
|
|
the ring updates to match the new port.
|