Swift Proxy
- OpenStack Charmers
- Cloud
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 197 | 15 Nov 2024 | |
latest/edge | 196 | 15 Nov 2024 | |
latest/edge | 195 | 15 Nov 2024 | |
latest/edge | 194 | 15 Nov 2024 | |
latest/edge | 184 | 29 May 2024 | |
latest/edge | 174 | 27 Oct 2023 | |
latest/edge | 159 | 06 Apr 2023 | |
latest/edge | 146 | 06 Sep 2022 | |
latest/edge | 58 | 17 Dec 2020 | |
latest/edge | 50 | 17 Dec 2020 | |
yoga/stable | 180 | 02 Dec 2023 | |
zed/stable | 181 | 02 Dec 2023 | |
xena/stable | 177 | 02 Dec 2023 | |
wallaby/stable | 179 | 02 Dec 2023 | |
victoria/stable | 169 | 12 Oct 2023 | |
ussuri/stable | 171 | 12 Oct 2023 | |
train/candidate | 153 | 28 Nov 2022 | |
train/edge | 167 | 12 Oct 2023 | |
stein/candidate | 153 | 28 Nov 2022 | |
stein/edge | 167 | 12 Oct 2023 | |
rocky/candidate | 153 | 28 Nov 2022 | |
rocky/edge | 167 | 12 Oct 2023 | |
queens/candidate | 153 | 28 Nov 2022 | |
queens/edge | 167 | 12 Oct 2023 | |
2024.1/candidate | 183 | 24 May 2024 | |
2024.1/candidate | 174 | 24 Jan 2024 | |
2023.2/stable | 176 | 30 Nov 2023 | |
2023.1/stable | 178 | 02 Dec 2023 |
juju deploy swift-proxy --channel yoga/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
add-user
Add a user to swauth. This adds a given user / pass to swauth. Auth-type must be set to swauth. Note that swauth is not supported for OpenStack Train and later.
- Params
-
account string
account to add this user to
-
password string
password for the newly created user
-
username string
username for the newly created user
- Required
account, username, password
-
diskusage
Run swift-recon -d on the specified unit. Returns values in GB.
-
dispersion-populate
Run swift-dispersion-populate command on the specified unit.
-
dispersion-report
Run swift-dispersion-report command on the specified unit.
-
openstack-upgrade
Perform openstack upgrades. Config option action-managed-upgrade must be set to True.
-
pause
Pause swift-proxy services. If the swift-proxy deployment is clustered using the hacluster charm, the corresponding hacluster unit on the node must first be paused as well. Not doing so may lead to an interruption of service.
-
remove-devices
Removes the device(s) from the ring. This should normally just be used for a device that has failed. For a device you wish to decommission, it's best to set its weight to 0, wait for it to drain all its data, then use this remove-from-ring action.
- Params
-
ring string
Swift ring to remove the device(s) from. Valid options are 'account', 'container', 'object' or 'all'.
-
search-value string
The search-value can be of the form: . d<device_id>r<region>z<zone>-<ip>:<port>R<r_ip>:<r_port>/ <device_name>_<meta> . Where <r_ip> and <r_port> are replication ip and port. Any part is optional, but you must include at least one part.
- Required
ring, search-value
-
resume
Resume swift-proxy services. If the swift-proxy deployment is clustered using the hacluster charm, the corresponding hacluster unit on the node must be resumed as well.
-
set-weight
Sets the device's weight.
- Params
-
ring string
Swift ring to set the weight for. Valid options are 'account', 'container', 'object' or 'all'.
-
search-value string
The search-value can be of the form: . d<device_id>r<region>z<zone>-<ip>:<port>R<r_ip>:<r_port>/ <device_name>_<meta> . Where <r_ip> and <r_port> are replication ip and port. Any part is optional, but you must include at least one part.
-
weight number
The device's weight
- Required
ring, search-value, weight