This change adds an admin-access interface to pass the admin credentials and api endpoint details to another charm. The dashboard charm uses this information registern the iscsi gateways with the dashboard. Change-Id: I5336ecab6a08e71dda22ba0347b8bee2f5683c3f
|2 months ago|
|src||1 month ago|
|templates||1 month ago|
|tests||5 months ago|
|unit_tests||1 month ago|
|.gitignore||1 year ago|
|.gitmodules||1 year ago|
|.gitreview||1 year ago|
|.jujuignore||1 year ago|
|.stestr.conf||2 years ago|
|.zuul.yaml||1 year ago|
|README.md||10 months ago|
|actions.yaml||1 year ago|
|build-requirements.txt||5 months ago|
|config.yaml||1 year ago|
|copyright||1 year ago|
|metadata.yaml||1 month ago|
|osci.yaml||1 month ago|
|requirements.txt||1 month ago|
|test-requirements.txt||1 year ago|
|tox.ini||8 months ago|
config.yaml for the full list of options, along with their
descriptions and default values.
Ceph BlueStore compression
This charm supports [BlueStore inline compression][ceph-bluestore-compression]
for its associated Ceph storage pool(s). The feature is enabled by assigning a
compression mode via the
bluestore-compression-mode configuration option. The
default behaviour is to disable compression.
The efficiency of compression depends heavily on what type of data is stored in the pool and the charm provides a set of configuration options to fine tune the compression behaviour.
Note: BlueStore compression is supported starting with Ceph Mimic.
We are assuming a pre-existing Ceph cluster.
To provide multiple data paths to clients deploy exactly two ceph-iscsi units:
juju deploy -n 2 ceph-iscsi
Then add a relation to the ceph-mon application:
juju add-relation ceph-iscsi:ceph-client ceph-mon:client
Deploying four ceph-iscsi units is theoretically possible but it is not an officially supported configuration.
The ceph-iscsi application cannot be containerised.
Co-locating ceph-iscsi with another application is only supported with ceph-osd, although doing so with other applications may still work.
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 ceph-iscsi. If the charm is not
deployed then see file
To display action descriptions run
juju actions ceph-iscsi. If the charm is
not deployed then see file
iSCSI target management
Create an iSCSI target
An iSCSI target can be created easily with the charm's
juju run-action --wait ceph-iscsi/0 create-target \ client-initiatorname=iqn.1993-08.org.debian:01:aaa2299be916 \ client-username=myiscsiusername \ client-password=myiscsipassword \ image-size=5G \ image-name=small \ pool-name=images
In the above, all option values are generally user-defined with the exception
of the initiator name (
client-initiatorname). An iSCSI initiator is
essentially an iSCSI client and so its name is client-dependent. Some
initiators may impose policy on credentials (
Important: The underlying machines for the ceph-iscsi units must have internal name resolution working (i.e. the machines must be able to resolve each other's hostnames).
The management of targets, beyond the target-creation action described above,
can be accomplished via the
gwcli utility. This CLI tool has its own shell,
and is available from any ceph-iscsi unit:
juju ssh ceph-iscsi/1 sudo gwcli /> help
Please report bugs on Launchpad.
For general charm questions refer to the OpenStack Charm Guide.