af3ba49948
* Enable running under tox 4 * add jammy-antelope, and jammy-zed bundles; remove focal-ussuri * Update osci.yaml so that it runs with charmcraft 2.1/stable Change-Id: I49d3d39e4b9052d50a5fa2f2f826b88ad92f7516 |
||
|---|---|---|
| .vscode | ||
| src | ||
| tests | ||
| unit_tests | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| charmcraft.yaml | ||
| config.yaml | ||
| metadata.yaml | ||
| osci.yaml | ||
| README.md | ||
| rename.sh | ||
| requirements.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
Overview
This charm implements Cinder charm subordinate that enables and configures the Infinidat storage backend for use with Charmed Openstack.
This charm is intended to work next to charm-infinidat-tools which configures the environment for using iSCSI and FC.
Note
: The cinder-infinidat charm is currently in tech-preview.
Configuration
To display all configuration option information run juju config <application>.
If the application is not deployed then see the charm's
Configure tab in the Charmhub. Finally,
the Juju documentation provides general guidance
on configuring applications.
Deployment
The charm can be deployed through a bundle or manually like described below:
juju deploy cinder --channel <channel>
juju deploy cinder-infinidat --channel <channel>
juju add-relation cinder-infinidat:storage-backend cinder:storage-backend
Infinidat configuration option validation
The charm deploys to blocked state unless all the mandatory configuration options for the Infinidat storage backend are properly set in the charm. Refer to Configure tab in the Charmhub for more information.
TLS encryption support
The charm supports configuring encrypted communication with Infinidat API and installation of the CA certificates.
Refer to Configure tab in the Charmhub for more information.
High availability
The charm can be used to enable Infinidat backend in highly available Charmed Cinder deployments.
Deferred service events
This charm supports the deferred service events feature.
Operational or maintenance procedures applied to a cloud often lead to the restarting of various OpenStack services and/or the calling of certain charm hooks. Although normal, such events can be undesirable due to the service interruptions they can cause.
The deferred service events feature provides the operator the choice of preventing these service restarts and hook calls from occurring, which can then be resolved at a more opportune time.
See Deferred service events for more information on this feature.
Documentation
The OpenStack Charms project maintains two documentation guides:
- OpenStack Charm Guide: the primary source of information for OpenStack charms
- OpenStack Charms Deployment Guide: a step-by-step guide for deploying OpenStack with charms
Bugs
Please report bugs on Launchpad.