Juju Charm - Ceph RADOS Gateway
Go to file
Ryan Beisner 88bd5777cf Update tox.ini files from release-tools gold copy
All OpenStack Charms now contain identical tox.ini files,
not to be modified or made unique within each charm repo.

This is to ensure consistency across charm repos in tox
target naming, approach and purpose, also giving the
charm dev and test experience additional consistency.

Also create empty dirs with .keep files where necessary.
Some classic charms have actions and/or lib dirs, and some
do not. In all classic charms, flake will now check those
dirs to ensure lint coverage of existing or future content.

Change-Id: I23cfd47fcee90678b4ba818ddc1d9ace4edd54f3
2016-09-09 19:21:59 +00:00
actions Re-license charm as Apache-2.0 2016-06-28 12:06:58 +01:00
files/www [hopem,r=] 2015-11-25 11:09:14 +00:00
hooks Pre 1607 release charm-helpers sync 2016-07-21 14:26:34 +00:00
lib Update tox.ini files from release-tools gold copy 2016-09-09 19:21:59 +00:00
templates Increase rgw init timeout to 1200 seconds 2016-06-17 12:52:25 +01:00
tests Use bundletester for amulet test execution 2016-07-21 18:13:52 +00:00
unit_tests Add rgw-buckets-pool-weight option for calculating pgs 2016-07-14 07:58:47 -07:00
.coveragerc Finsh unit tests and fix lint 2015-02-10 10:30:13 +00:00
.gitignore Add Juju Network Space support 2016-03-31 13:05:19 +01:00
.gitreview Add gitreview prior to migration to openstack 2016-02-24 21:53:29 +00:00
.project Add pydev stuff 2014-01-24 17:20:33 +00:00
.pydevproject Add pydev stuff 2014-01-24 17:20:33 +00:00
.testr.conf Add tox support 2015-11-03 11:58:54 +00:00
actions.yaml Add pause/resume actions and sync charm-helpers 2016-03-29 10:31:28 +00:00
charm-helpers-hooks.yaml Add support for user-provided ceph config 2016-06-01 11:34:59 +01:00
charm-helpers-tests.yaml Move charm-helpers-sync.yaml to charm-helpers-hooks.yaml and 2014-09-27 02:57:08 +00:00
config.yaml Add rgw-buckets-pool-weight option for calculating pgs 2016-07-14 07:58:47 -07:00
copyright Re-license charm as Apache-2.0 2016-06-28 12:06:58 +01:00
hardening.yaml Add hardening support 2016-03-24 11:37:10 +00:00
icon.svg Adding Ceph icon. 2013-07-17 00:23:14 -05:00
LICENSE Re-license charm as Apache-2.0 2016-06-28 12:06:58 +01:00
Makefile Use bundletester for amulet test execution 2016-07-21 18:13:52 +00:00
metadata.yaml Add Juju Network Space support 2016-03-31 13:05:19 +01:00
README.md DNS HA 2016-06-15 14:13:02 -07:00
requirements.txt Fix pbr requirement 2016-04-13 10:25:36 +00:00
revision [hopem] Added use-syslog cfg option to allow logging to syslog 2014-03-25 18:44:22 +00:00
test-requirements.txt Use bundletester for amulet test execution 2016-07-21 18:13:52 +00:00
TODO Added cephx support 2012-10-09 13:35:06 +01:00
tox.ini Update tox.ini files from release-tools gold copy 2016-09-09 19:21:59 +00:00

Overview

Ceph is a distributed storage and network file system designed to provide excellent performance, reliability and scalability.

This charm deploys the RADOS Gateway, a S3 and Swift compatible HTTP gateway for online object storage on-top of a ceph cluster.

Usage

In order to use this charm, it is assumed that you have already deployed a ceph storage cluster using the 'ceph' charm with something like this::

juju deploy -n 3 --config ceph.yaml ceph

To deploy the RADOS gateway simple do::

juju deploy ceph-radosgw juju add-relation ceph-radosgw ceph

You can then directly access the RADOS gateway by exposing the service::

juju expose ceph-radosgw

The gateway can be accessed over port 80 (as show in juju status exposed ports).

Access

Note that you will need to login to one of the service units supporting the ceph charm to generate some access credentials::

juju ssh ceph/0
'sudo radosgw-admin user create --uid="ubuntu" --display-name="Ubuntu Ceph"'

For security reasons the ceph-radosgw charm is not set up with appropriate permissions to administer the ceph cluster.

Keystone Integration

Ceph >= 0.55 integrates with Openstack Keystone for authentication of Swift requests.

This is enabled by relating the ceph-radosgw service with keystone::

juju deploy keystone juju add-relation keystone ceph-radosgw

If you try to relate the radosgw to keystone with an earlier version of ceph the hook will error out to let you know.

HA/Clustering

There are two mutually exclusive high availability options: using virtual IP(s) or DNS. In both cases, a relationship to hacluster is required which provides the corosync back end HA functionality.

To use virtual IP(s) the clustered nodes must be on the same subnet such that the VIP is a valid IP on the subnet for one of the node's interfaces and each node has an interface in said subnet. The VIP becomes a highly-available API endpoint.

At a minimum, the config option 'vip' must be set in order to use virtual IP HA. If multiple networks are being used, a VIP should be provided for each network, separated by spaces. Optionally, vip_iface or vip_cidr may be specified.

To use DNS high availability there are several prerequisites. However, DNS HA does not require the clustered nodes to be on the same subnet. Currently the DNS HA feature is only available for MAAS 2.0 or greater environments. MAAS 2.0 requires Juju 2.0 or greater. The clustered nodes must have static or "reserved" IP addresses registered in MAAS. The DNS hostname(s) must be pre-registered in MAAS before use with DNS HA.

At a minimum, the config option 'dns-ha' must be set to true and at least one of 'os-public-hostname', 'os-internal-hostname' or 'os-internal-hostname' must be set in order to use DNS HA. One or more of the above hostnames may be set.

The charm will throw an exception in the following circumstances: If neither 'vip' nor 'dns-ha' is set and the charm is related to hacluster If both 'vip' and 'dns-ha' are set as they are mutually exclusive If 'dns-ha' is set and none of the os-{admin,internal,public}-hostname(s) are set

Network Space support

This charm supports the use of Juju Network Spaces, allowing the charm to be bound to network space configurations managed directly by Juju. This is only supported with Juju 2.0 and above.

API endpoints can be bound to distinct network spaces supporting the network separation of public, internal and admin endpoints.

To use this feature, use the --bind option when deploying the charm:

juju deploy ceph-radosgw --bind "public=public-space internal=internal-space admin=admin-space"

alternatively these can also be provided as part of a juju native bundle configuration:

ceph-radosgw:
  charm: cs:xenial/ceph-radosgw
  num_units: 1
  bindings:
    public: public-space
    admin: admin-space
    internal: internal-space

NOTE: Spaces must be configured in the underlying provider prior to attempting to use them.

NOTE: Existing deployments using os-*-network configuration options will continue to function; these options are preferred over any network space binding provided if set.

Contact Information

Author: James Page james.page@ubuntu.com Report bugs at: http://bugs.launchpad.net/charms/+source/ceph-radosgw/+filebug Location: http://jujucharms.com/charms/ceph-radosgw

Bootnotes

The Ceph RADOS Gateway makes use of a multiverse package libapache2-mod-fastcgi. As such it will try to automatically enable the multiverse pocket in /etc/apt/sources.list. Note that there is noting 'wrong' with multiverse components - they typically have less liberal licensing policies or suchlike.