This is to enable other charms to pass there enable-focal patchsets. The pre-enable is simply to sync in charmhelpers with py38 support so that this charm can participate in swift-proxy's focal enablement. Change-Id: Ic94761fd65e9f442fa08315bbbdc377d7d0a97c9
|1 settimana fa|
|actions||1 anno fa|
|charmhelpers||1 settimana fa|
|files||1 anno fa|
|hooks||1 mese fa|
|lib||3 mesi fa|
|templates||3 mesi fa|
|tests||2 mesi fa|
|unit_tests||3 mesi fa|
|.gitignore||1 anno fa|
|.gitreview||11 mesi fa|
|.project||6 anni fa|
|.pydevproject||2 anni fa|
|.stestr.conf||1 anno fa|
|.zuul.yaml||3 mesi fa|
|LICENSE||3 anni fa|
|Makefile||1 anno fa|
|README.md||1 mese fa|
|actions.yaml||4 anni fa|
|charm-helpers-hooks.yaml||6 mesi fa|
|config.yaml||3 mesi fa|
|copyright||3 anni fa|
|hardening.yaml||4 anni fa|
|icon.svg||2 anni fa|
|metadata.yaml||1 mese fa|
|requirements.txt||1 anno fa|
|revision||6 anni fa|
|setup.cfg||8 mesi fa|
|test-requirements.txt||5 mesi fa|
|tox.ini||5 mesi fa|
OpenStack Swift is a highly available, distributed, eventually consistent object/blob store.
The swift-storage charm deploys Swift's storage component. The charm's basic function is to initialise storage devices and manage the container, object, and account services. It works in tandem with the swift-proxy charm, which is used to add proxy nodes.
This section covers common configuration options. See file
the full list of options, along with their descriptions and default values.
zone option assigns a storage zone (an integer) to a storage node. A zone
is associated with data replicas.
block-device option specifies the device(s) that will be used on all
machines associated with the application. Value types include:
The resulting block device(s) will be XFS-formatted and use
/srv/node/<device-name> as a mount point.
storage-region option specifies a storage region (an integer). It is used
only for multi-region (global) clusters.
swift.yaml contain the deployment configuration:
swift-proxy: zone-assignment: manual replicas: 3 swift-storage-zone1: zone: 1 block-device: /dev/sdb swift-storage-zone2: zone: 2 block-device: /dev/sdb swift-storage-zone3: zone: 3 block-device: /dev/sdb
Deploy the proxy and storage nodes:
juju deploy --config swift.yaml swift-proxy juju deploy --config swift.yaml swift-storage swift-storage-zone1 juju deploy --config swift.yaml swift-storage swift-storage-zone2 juju deploy --config swift.yaml swift-storage swift-storage-zone3
Add relations between the proxy node and all storage nodes:
juju add-relation swift-proxy:swift-storage swift-storage-zone1:swift-storage juju add-relation swift-proxy:swift-storage swift-storage-zone2:swift-storage juju add-relation swift-proxy:swift-storage swift-storage-zone3:swift-storage
This will result in a three-zone cluster, with each zone consisting of a single storage node, thereby satisfying the replica requirement of three.
Storage capacity is increased by adding swift-storage units to a zone. For example, to add two storage nodes to zone ‘3’:
juju add-unit -n 2 swift-storage-zone3
Note: When scaling out ensure the candidate machines are equipped with the block devices currently configured for the associated application.
This charm will not balance the storage ring until there are enough storage zones to meet its minimum replica requirement, in this case three.
This section covers Juju actions supported by the charm. Actions allow specific operations to be performed on a per-unit basis.
To display action descriptions run
juju actions swift-storage.
Please report bugs on Launchpad.
For general charm questions refer to the OpenStack Charm Guide.