Commit Graph

20 Commits

Author SHA1 Message Date
Jake Nabasny 2380ad7cde Update command references to juju 3.x syntax
Change-Id: I4f1e1bbcf43a55b465382af914a0951aedf8c62b

Change "relate" to "integrate" in README juju cmd

Change-Id: I4f1e1bbcf43a55b465382af914a0951aedf8c62b
2023-09-20 12:07:47 -04:00
Samuel Walladge f3d67ff89d Clarify that osd-devices not present are ignored
This means that for cases where servers may have a different
number of disks, the same application can be deployed across all,
listing all disks in the osd-devices option.
Any devices in the list that aren't found on the server
will simply be ignored.

Change-Id: I7d0e32571845f790bb1ec42aa6eef72cc9b57b38
2023-07-31 15:02:57 +09:30
Peter Matulis 313e71bc7b Fix README, extraneous options line
Change-Id: I8e5b48de0662c99fffca56a9a48111e75d9bc543
2021-11-30 19:32:01 -05:00
Felipe Reyes c5a2f2f776 Clear the default value for osd-devices
Using /dev/vdb as default can go in conflict when using juju storage to
attach devices dynamically as OSD and journal, because juju may be
attaching as the first disk a volume that's meant to be used as a
journal and making the list of devices overlap.

Change-Id: I97c7657a82ea463aa090fc6266a4988c8c6bfeb4
Closes-Bug: #1946504
2021-10-08 16:44:44 -03:00
Robert Gildein d0d3d3edf5 Add an action to provide information about AZ
The 'get-availability-zone' action will get information about an
availability zone that will contain information about the CRUSH
structure. Specifically 'rack' and 'row'.

Closes-Bug: #1911006
Change-Id: I99ebbef5f23d6efe3c848b089c7f2b0d26ad0077
2021-09-03 09:48:24 +02:00
Peter Matulis f07f0632d5 Review action usage sections in README
* Correct and improve in/out and stop/start
  actions

* Make examples for all actions more consistent

* Add link to Charmed Ceph documentation

* Add a bug reference for the zap-disk action

* Small miscellaenous improvements

Change-Id: Iafa3cfce4c5b3eff599b662bfe2cfc3d9183cad3
2021-03-02 12:56:15 -05:00
Nicolas Bock 58c626d643
Fix wording for `osd-out` action
The `osd-out` action stops osds.

Signed-off-by: Nicolas Bock <nicolas.bock@canonical.com>
Change-Id: Idc23129a8ec39bc5451c9fae57b2045537b77777
2021-02-18 14:10:51 -07:00
Martin Kalcok e22f602544 Added `start` and `stop` actions for management of ceph OSDs
Change-Id: If8b83ab06364903548c5841487034bc1bb9aaf0c
Closes-Bug: #1477731
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/473
2020-12-15 17:29:24 +01:00
Peter Matulis a88ef0c5e7 Expose BlueStore
Explain how BlueStore vs traditional filesystems
are selected.

Improve config.yaml correspondingly. Move the
'bluestore' option's location in that file. Remove
blank lines for consistency.

Change-Id: Iebc21bdcac742a437719afb53f26729abbf8e87f
2020-10-13 14:21:58 -04:00
Peter Matulis 05c9f0c70c Fix ordered list
Change-Id: Iffef8787165dfbda35df0ad047f59e4a38288a39
2020-08-26 09:17:37 -04:00
Peter Matulis cabeb9b784 Improve zap-disk action section
Also fix an ordered list that was not rendering
properly in the Charm Store.

Change-Id: Ibd8ea8919e80bf332b6f2509739b5e6055e081dc
2020-08-25 16:27:21 -04:00
Peter Matulis 07e85175d9 Improve README
This improvement is part of a wave of polish
in preparation for the launch of the Ceph product.

In config.yaml, improve 'osd-journal' option description.
Also modernise example values for 'source' and use
consistent words with the ceph-osd, ceph-mon, and ceph-fs
charms.

Change-Id: Iefbf57078115181c67b320e0c5b6cbd7dc05ac55
2020-07-22 12:34:41 -04:00
Peter Matulis 8daad68ebd Format based on README template
Change-Id: I51163b690cc80158d63ad00cba3d6b6e84833b2e
2020-05-14 11:21:19 -04:00
Peter Matulis c6b46f2bd2 Comprehensive review of ceph-osd README
Review of README.

Corrected doc URLs in actions.yaml.

The trailing spaces on these lines are deliberate
(forces a carriage return):

260
265
291
307
332
337

Change-Id: Ia61edbfcbf27bf9bc6b35a71793df39c7cb46907
2020-02-04 11:48:01 -05:00
Frode Nordahl 5c0bef38d3
Make action descriptions terse, move to README.md
Output of `juju list-action` is at time of this writing
formatted in such a way that we should keep description
as terse as possible and refer to documentation elsewhere.

Change-Id: Ib8e7a4804e696199803b9ac386da7bf02aafd465
2018-06-05 13:52:05 +02:00
Frode Nordahl 8a1e2e548b
Update README.md with information on initializing disks
Weed out some references to the now deprecated `ceph` charm.

Add example of juju storage usage and reference to juju storage
documentation.

Change-Id: Ia9955e2b49589072fd2e1d265a88439d4aebe511
2018-06-05 08:42:19 +02:00
James Page 2069e620b7 Add support for vault key management with vaultlocker
vaultlocker provides support for storage of encryption keys
for LUKS based dm-crypt device in Hashicorp Vault.

Add support for this key management approach for Ceph
Luminous or later.   Applications will block until vault
has been initialized and unsealed at which point OSD devices
will be prepared and booted into the Ceph cluster.

The dm-crypt layer is placed between the block device
parition and the top level LVM PV used to create VG's
and LV's to support OSD operation.

Vaultlocker enables a systemd unit for each encrypted
block device to perform unlocking during reboots of the
unit; ceph-volume will then detect the new VG/LV's and
boot the ceph-osd processes as required.

Note that vault/vaultlocker usage is only supported with
ceph-volume, which was introduced into the Ubuntu packages
as of the 12.2.4 point release for Luminous.  If vault is
configured as the key manager in deployments using older
versions, a hook error will be thrown with a blocked
status message to this effect.

Change-Id: I713492d1fd8d371439e96f9eae824b4fe7260e47
Depends-On: If73e7bd518a7bc60c2db08e2aa3a93dcfe79c0dd
Depends-On: https://github.com/juju/charm-helpers/pull/159
2018-05-15 08:28:15 +01:00
Ryan Beisner 2036e2ea39 Update readme for apparmor
Change-Id: I4afe123e8543441a9fee805dea1426ddd19a9416
2018-03-28 13:36:55 -05:00
James Page afe7651e5c Add support for Juju network spaces
Juju 2.0 provides support for network spaces, allowing
charm authors to support direct binding of relations and
extra-bindings onto underlying network spaces.

Add public and cluster extra bindings to this charm to
support separation of client facing and cluster network
traffic using Juju network spaces.

Existing network configuration options will still be
preferred over any Juju provided network bindings, ensuring
that upgrades to existing deployments don't break.

Change-Id: I78ab6993ad5bd324ea52e279c6ca2630f965544c
2016-04-08 22:42:36 +01:00
James Page 80b4985348 Resync with ceph charm, updates for raring 2012-12-17 10:31:03 +00:00