Openstack Nova Volume service provides EBS-like storage to Openstack instances.
This charm will configure Nova volume on a given unit to serve logical volumes
over iSCSI via the nova-volume service. All communication between nova-volume
and the rest of the Openstack deployment happens over the database and
messaging queue thus the charm has two required relations: mysql:shared-db and
rabbitmq:amqp.
To deploy along side an existing Openstack deployment, simply:
juju deploy --repository=. local:nova-volume
juju add-relation mysql nova-volume
juju add-relation rabbitmq nova-volume
Assuming the rest of the Openstack cloud is functioning properly,
the volume service will come online.
Overview of config options and corresponding defaults:
nova-release: distro
From which installation source to install the required Nova packages.
The default is to install from the Ubuntu archive. You may also specify
one of the following:
- trunk: upstream trunk PPA (ppa:nova-core/trunk)
- milestone: upstream milestone PPA (ppa:nova-core/milestone)
- milestone-proposed: upstream milestone PPA
(ppa:nova-core/milestone-proposed)
- A valid PPA with in LP PPA format: ppa:myaccount/ppaname
- A custom URL formated ala:
'deb http://host/ubuntu oneiric main'
You may append a GPG Key ID to the end of the line after a |,
and the charm will attempt to import it from keyserver.ubuntu.com.
block-device: sdb
Nova Volume requires a volume group be created from which to carve out
logical volumes. This block device will be initialized as the physical volume
that backs this volume group.
You may use either /dev/<block-device>, <block-device>, or
/path/to/file[|size]. In the third format, '|size' is optional, defaulting
to 5G. Example: "/var/lib/nova-volumes/my-vol.img|2G". The size parameter
is passed to 'truncate --size'
volume-group: nova-volumes
The volume group to create and use when creating new volumes.
overwrite: false
By default, LVM2 and the charm will refuse to initialize a block device
that has existing LVM signatures or is mounted. If this is set to true, the
charm will attempt to unmount the block device if is mounted and wipe any
traces of LVM from it, prior to initializing it as a new volume group. *BEWARE*
rabbit-user: nova
Username with which to request access to the messaging queue.
rabbit-vhost: nova
Name of the RabbitMQ virtual host to access. This must be the same across all
Nova components.
db-user: nova
Database user with which to request access to the shared MySQL database.
nova-db: nova
Database to request access to. This must be the same across all Nova
components.
| 2012/11/21 Adam Gandelman Merge upstream. (revno 34) |
| 2012/11/21 Adam Gandelman Re-add QA special sauce. (revno 33) |
| 2012/11/21 Adam Gandelman Merge upstream changes. (revno 32) |
| 2012/08/24 Adam Gandelman Add access to folsom-deps-staging PPA for trunk deploys. (revno 31) |
| 2012/08/22 Adam Gandelman Merge (revno 30) |
| 2012/08/22 Adam Gandelman Setup access to ppa:openstack-ubuntu-testing/folsom-deps-staging (revno 29) |
| 2012/08/21 Adam Gandelman Add access to cloud archive. (revno 28) |
| 2012/06/15 Adam Gandelman Merge lp:~charmers/charms/quantal/nova-volume/trunk (revno 27) |
| 2012/06/08 Adam Gandelman Save tested package versions to /tmp/versions_tested. (revno 26) |