Openstack Charmers Next Cinder

  • By OpenStack Charmers - Testing Charms
  • Cloud
Channel Revision Published Runs on
latest/stable 1404 09 Feb 2022
Ubuntu 21.10 Ubuntu 20.04
latest/edge 698 19 Mar 2021
Ubuntu 15.10
juju deploy openstack-charmers-next-cinder
Show information

Platform:

Ubuntu
21.10 20.04

Learn about configurations >

  • action-managed-upgrade | boolean

    If True enables openstack upgrades for this charm via juju actions. You will still need to set openstack-origin to the new repository but instead of an upgrade running automatically across all units, it will wait for you to execute the openstack-upgrade action for this charm on each unit. If False it will revert to existing behavior of upgrading all units on config change.

  • api-listening-port | int

    Default: 8776

    OpenStack Volume API listening port.

  • block-device | string

    Default: sdb

    Set to 'None' for deployments whose storage is managed by separate charms (cinder-lvm, cinder-netapp, ceph-mon). . The below LVM functionality is DEPRECATED. Use the cinder-lvm charm instead. . The block devices on which to create LVM volume group. . This can also be a space-delimited list of block devices to attempt to use in the cinder LVM volume group - each block device detected will be added to the available physical volumes in the volume group. . May be set to the path and size of a local file (/path/to/file.img|$sizeG), which will be created and used as a loopback device (for testing only). $sizeG defaults to 5G

  • ceph-osd-replication-count | int

    Default: 3

    This value dictates the number of replicas ceph must make of any object it stores within the cinder rbd pool. Of course, this only applies if using Ceph as a backend store. Note that once the cinder rbd pool has been created, changing this value will not have any effect (although the configuration of a pool can be always be changed within ceph itself or via the charm used to deploy ceph).

  • config-flags | string

    Comma-separated list of key=value config flags. These values will be placed in the cinder.conf [DEFAULT] section.

  • database | string

    Default: cinder

    Database to request access.

  • database-user | string

    Default: cinder

    Username to request database access.

  • debug | boolean

    Enable debug logging.

  • default-volume-type | string

    The default volume type when creating a new volume without a volume type specified. It's useful only when multiple storage backends to be connected to Cinder. The corresponding volume type must be created after a deployment via API to take effect, e.g., `openstack volume type create VOLUME_TYPE --property volume_backend_name=BACKEND_NAME`

  • dns-ha | boolean

    Use DNS HA with MAAS 2.0. Note if this is set do not set vip settings below.

  • enabled-services | string

    Default: all

    If splitting cinder services between units, define which services to install and configure.

  • ephemeral-unmount | string

    The below LVM functionality is DEPRECATED. Use the cinder-lvm charm instead. . Cloud instances provide ephemeral storage which is normally mounted on /mnt. . Providing this option will force an unmount of the ephemeral device so that it can be used as a Cinder storage device. This is useful for testing purposes (cloud deployment is not a typical use case).

  • glance-api-version | int

    Default: 1

    Newer storage drivers may require the v2 Glance API to perform certain actions e.g. the RBD driver requires requires this to support COW cloning of images. This option will default to v1 for backwards compatibility with older glance services.

  • ha-bindiface | string

    Default: eth0

    Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.

  • ha-mcastport | int

    Default: 5454

    Default multicast port number that will be used to communicate between HA Cluster nodes.

  • haproxy-client-timeout | int

    Client timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 90000ms is used.

  • haproxy-connect-timeout | int

    Connect timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 9000ms is used.

  • haproxy-queue-timeout | int

    Queue timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 9000ms is used.

  • haproxy-server-timeout | int

    Server timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 90000ms is used.

  • harden | string

    Apply system hardening. Supports a space-delimited list of modules to run. Supported modules currently include os, ssh, apache and mysql.

  • image-volume-cache-enabled | boolean

    Enable the image volume cache. Supported on OpenStack Ocata and newer.

  • image-volume-cache-max-count | int

    Max number of entries allowed in the image volume cache. 0 means unlimited. Supported on OpenStack Ocata and newer.

  • image-volume-cache-max-size-gb | int

    Max size of the image volume cache in GB. 0 means unlimited. Supported on OpenStack Ocata and newer.

  • nagios_context | string

    Default: juju

    Used by the nrpe-external-master subordinate charm. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like 'juju-myservice-0'. If you are running multiple environments with the same services in them this allows you to differentiate between them.

  • nagios_servicegroups | string

    A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup

  • notification-topics | string

    A comma-separated list of oslo notification topics. If left empty, the default topic 'cinder' is going to be used.

  • openstack-origin | string

    Default: yoga

    Repository from which to install. May be one of the following: distro (default), ppa:somecustom/ppa, a deb url sources entry, or a supported Ubuntu Cloud Archive e.g. . cloud:<series>-<openstack-release> cloud:<series>-<openstack-release>/updates cloud:<series>-<openstack-release>/staging cloud:<series>-<openstack-release>/proposed . See https://wiki.ubuntu.com/OpenStack/CloudArchive for info on which cloud archives are available and supported. . NOTE: updating this setting to a source that is known to provide a later version of OpenStack will trigger a software upgrade unless action-managed-upgrade is set to True.

  • os-admin-hostname | string

    The hostname or address of the admin endpoints created for cinder in the keystone identity provider. . This value will be used for admin endpoints. For example, an os-admin-hostname set to 'cinder.admin.example.com' with ssl enabled will create two admin endpoints for cinder: . https://cinder.admin.example.com:443/v2/$(tenant_id)s and https://cinder.admin.example.com:443/v3/$(tenant_id)s

  • os-admin-network | string

    The IP address and netmask of the OpenStack Admin network (e.g. 192.168.0.0/24) . This network will be used for admin endpoints.

  • os-internal-hostname | string

    The hostname or address of the internal endpoints created for cinder in the keystone identity provider. . This value will be used for internal endpoints. For example, an os-internal-hostname set to 'cinder.internal.example.com' with ssl enabled will create two internal endpoints for cinder: . https://cinder.internal.example.com:443/v2/$(tenant_id)s and https://cinder.internal.example.com:443/v3/$(tenant_id)s

  • os-internal-network | string

    The IP address and netmask of the OpenStack Internal network (e.g. 192.168.0.0/24) . This network will be used for internal endpoints.

  • os-public-hostname | string

    The hostname or address of the public endpoints created for cinder in the keystone identity provider. . This value will be used for public endpoints. For example, an os-public-hostname set to 'cinder.example.com' with ssl enabled will create two public endpoints for cinder: . https://cinder.example.com:443/v2/$(tenant_id)s and https://cinder.example.com:443/v3/$(tenant_id)s

  • os-public-network | string

    The IP address and netmask of the OpenStack Public network (e.g. 192.168.0.0/24) . This network will be used for public endpoints.

  • overwrite | string

    Default: false

    The below LVM functionality is DEPRECATED. Use the cinder-lvm charm instead. . If true, charm will attempt to overwrite block devices containing previous filesystems or LVM, assuming it is not in use.

  • prefer-ipv6 | boolean

    If True enables IPv6 support. The charm will expect network interfaces to be configured with an IPv6 address. If set to False (default) IPv4 is expected. . NOTE: these charms do not currently support IPv6 privacy extension. In order for this charm to function correctly, the privacy extension must be disabled and a non-temporary address must be configured/available on your network interface.

  • rabbit-user | string

    Default: cinder

    Username to request access on rabbitmq-server.

  • rabbit-vhost | string

    Default: openstack

    RabbitMQ virtual host to request access on rabbitmq-server.

  • region | string

    Default: RegionOne

    OpenStack Region

  • remove-missing | boolean

    The below LVM functionality is DEPRECATED. Use the cinder-lvm charm instead. . If True, charm will attempt to remove missing physical volumes from volume group, if logical volumes are not allocated on them.

  • remove-missing-force | boolean

    The below LVM functionality is DEPRECATED. Use the cinder-lvm charm instead. . If True, charm will attempt to remove missing physical volumes from volume group, even when logical volumes are allocated on them. This option overrides 'remove-missing' when set.

  • restrict-ceph-pools | boolean

    Cinder can optionally restrict the key it asks Ceph for to only be able to access the pools it needs.

  • scheduler-default-filters | string

    List of comma-separated filter class names to use for filtering hosts when not specified in the request. The default filters varies based on OpenStack release.

  • ssl_ca | string

    SSL CA to use with the certificate and key provided - this is only required if you are providing a privately signed ssl_cert and ssl_key.

  • ssl_cert | string

    SSL certificate to install and use for API ports. Setting this value and ssl_key will enable reverse proxying, point Cinder's entry in the Keystone catalog to use https, and override any certificate and key issued by Keystone (if it is configured to do so).

  • ssl_key | string

    SSL key to use with certificate specified as ssl_cert.

  • use-internal-endpoints | boolean

    Openstack mostly defaults to using public endpoints for internal communication between services. If set to True this option will configure services to use internal endpoints where possible.

  • use-policyd-override | boolean

    If True then use the resource file named 'policyd-override' to install override YAML files in the service's policy.d directory. The resource file should be a ZIP file containing at least one yaml file with a .yaml or .yml extension. If False then remove the overrides.

  • use-syslog | boolean

    Setting this to True will allow supporting services to log to syslog.

  • verbose | boolean

    Enable verbose logging.

  • vip | string

    Virtual IP(s) to use to front API services in HA configuration. . If multiple networks are being used, a VIP should be provided for each network, separated by spaces.

  • vip_cidr | int

    Default: 24

    Default CIDR netmask to use for HA vip when it cannot be automatically determined.

  • vip_iface | string

    Default: eth0

    Default network interface to use for HA vip when it cannot be automatically determined.

  • volume-group | string

    Default: cinder-volumes

    Name of volume group to create and store Cinder volumes.

  • volume-usage-audit-period | string

    Default: month

    Time period for which to generate volume usages. The options are hour, day, month, or year.

  • worker-multiplier | float

    The CPU core multiplier to use when configuring worker processes for this service. By default, the number of workers for each daemon is set to twice the number of CPU cores a service unit has. This default value will be capped to 4 workers unless this configuration option is set.