Hopem Nova Compute Nova Network
- By Edward Hope-Morley
- Cloud
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 0 | 19 Mar 2021 |
juju deploy hopem-nova-compute-nova-network
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
aa-profile-mode | string
Default: disable
Experimental enable apparmor profile. Valid settings: 'complain', 'enforce' or 'disable'. . AA disabled by default.
-
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.
-
authorized-keys-path | string
Default: {homedir}/.ssh/authorized_keys
Only used when migration-auth-type is set to ssh. . Full path to authorized_keys file, can be useful for systems with non-default AuthorizedKeysFile location. It will be formatted using the following variables: . homedir - user's home directory username - username .
-
bridge-interface | string
Default: br100
Bridge interface to be configured.
-
bridge-ip | string
Default: 11.0.0.1
IP to be assigned to bridge interface.
-
bridge-netmask | string
Default: 255.255.255.0
Netmask to be assigned to bridge interface.
-
ceph-osd-replication-count | int
Default: 3
This value dictates the number of replicas ceph must make of any object it stores within the nova rbd pool. Of course, this only applies if using Ceph as a backend store. Note that once the nova rbd pool has been created, changing this value will not have any effect (although it can be changed in ceph by manually configuring your ceph cluster).
-
ceph-pool-weight | int
Default: 30
Defines a relative weighting of the pool as a percentage of the total amount of data in the Ceph cluster. This effectively weights the number of placement groups for the pool created to be appropriately portioned to the amount of data expected. For example, if the ephemeral volumes for the OpenStack compute instances are expected to take up 20% of the overall configuration then this value would be specified as 20. Note - it is important to choose an appropriate value for the pool weight as this directly affects the number of placement groups which will be created for the pool. The number of placement groups for a pool can only be increased, never decreased - so it is important to identify the percent of data that will likely reside in the pool.
-
config-flags | string
Comma-separated list of key=value config flags. These values will be placed in the nova.conf [DEFAULT] section.
-
cpu-mode | string
Set to 'host-model' to clone the host CPU feature flags; to 'host-passthrough' to use the host CPU model exactly; to 'custom' to use a named CPU model; to 'none' to not set any CPU model. If virt_type='kvm|qemu', it will default to 'host-model', otherwise it will default to 'none'. Defaults to 'host-passthrough' for ppc64el, ppc64le if no value is set.
-
cpu-model | string
Set to a named libvirt CPU model (see names listed in /usr/share/libvirt/cpu_map.xml). Only has effect if cpu_mode='custom' and virt_type='kvm|qemu'.
-
cpu-model-extra-flags | string
Space delimited list of specific CPU flags for libvirt.
-
database | string
Default: nova
Nova database name.
-
database-user | string
Default: nova
Username for database access.
-
debug | boolean
Enable debug logging.
-
default-availability-zone | string
Default: nova
Default compute node availability zone. . This option determines the availability zone to be used when it is not specified in the VM creation request. If this option is not set, the default availability zone 'nova' is used. . NOTE: Availability zones must be created manually using the 'openstack aggregate create' command. .
-
disk-cachemodes | string
Specific cachemodes to use for different disk types e.g: file=directsync,block=none
-
enable-live-migration | boolean
Configure libvirt or lxd for live migration. . Live migration support for lxd is still considered experimental. . NOTE: This also enables passwordless SSH access for user 'root' between compute hosts.
-
enable-resize | boolean
Enable instance resizing. . NOTE: This also enables passwordless SSH access for user 'nova' between compute hosts.
-
encrypt | boolean
Encrypt block devices used for nova instances using dm-crypt, making use of vault for encryption key management; requires a relation to vault.
-
ephemeral-device | string
Block devices to use for storage of ephermeral disks to support nova instances; generally used in-conjunction with 'encrypt' to support data-at-rest encryption of instance direct attached storage volumes.
-
ephemeral-unmount | string
Cloud instances provide ephermeral storage which is normally mounted on /mnt. . Setting this option to the path of the ephemeral mountpoint will force an unmount of the corresponding device so that it can be used for as the backing store for local instances. This is useful for testing purposes (cloud deployment is not a typical use case).
-
flat-interface | string
Default: eth1
Network interface on which to build bridge.
-
force-raw-images | boolean
Default: True
Force conversion of backing images to raw format. Note that the conversion process in Pike uses O_DIRECT calls - certain file systems do not support this, for example ZFS; e.g. if using the LXD provider with ZFS backend, this option should be set to False.
-
harden | string
Apply system hardening. Supports a space-delimited list of modules to run. Supported modules currently include os, ssh, apache and mysql.
-
hugepages | string
The percentage of system memory to use for hugepages eg '10%' or the total number of 2M hugepages - eg "1024". For a systemd system (wily and later) the prefered approach is to enable hugepages via kernel parameters set in MAAS and systemd will mount them automatically. . NOTE: For hugepages to work it must be enabled on the machine deployed to. This can be accomplished by setting kernel parameters on capable machines in MAAS, tagging them and using these tags as constraints in the model.
-
instances-path | string
Path used for storing Nova instances data - empty means default of /var/lib/nova/instances.
-
ksm | string
Default: AUTO
Set to 1 to enable KSM, 0 to disable KSM, and AUTO to use default settings. . Please note that the AUTO value works for qemu 2.2+ (> Kilo), older releases will be set to 1 as default.
-
libvirt-image-backend | string
Tell Nova which libvirt image backend to use. Supported backends are raw, qcow2, rbd and flat. If no backend is specified, the Nova default (qcow2) is used. NOTE: "rbd" imagebackend is only supported with >= Juno. NOTE: "flat" imagebackend is only supported with >= Newton and replaces "raw".
-
migration-auth-type | string
Default: ssh
TCP authentication scheme for libvirt live migration. Available options include ssh.
-
multi-host | string
Default: yes
Whether to run nova-api and nova-network on the compute nodes.
-
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're 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.
-
nova-config | string
Default: /etc/nova/nova.conf
Full path to Nova configuration file.
-
openstack-origin | string
Default: distro
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 (UCA) release pocket. . Supported UCA sources include: . cloud:<series>-<openstack-release> cloud:<series>-<openstack-release>/updates cloud:<series>-<openstack-release>/staging cloud:<series>-<openstack-release>/proposed . For series=Precise we support UCA for openstack-release= * icehouse . For series=Trusty we support UCA for openstack-release= * juno * kilo * ... . NOTE: updating this setting to a source that is known to provide a later version of OpenStack will trigger a software upgrade. .
-
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 to bind vncproxy client.
-
pci-alias | string
The pci-passthrough-whitelist option of nova-compute charm is used for specifying which PCI devices are allowed passthrough. pci-alias is more a convenience that can be used in conjunction with Nova flavor properties to automatically assign required PCI devices to new instances. You could, for example, have a GPU flavor or a SR-IOV flavor: . pci-alias='{"vendor_id":"8086","product_id":"10ca","name":"a1"}' . This configures a new PCI alias 'a1' which will request a PCI device with a vendor id of 0x8086 and a product id of 10ca. . For more information about the syntax of pci_alias, refer to https://docs.openstack.org/ocata/config-reference/compute/config-options.html
-
pci-passthrough-whitelist | string
Sets the pci_passthrough_whitelist option in nova.conf which allows PCI passthrough of specific devices to VMs. . Example applications: GPU processing, SR-IOV networking, etc. . NOTE: For PCI passthrough to work IOMMU must be enabled on the machine deployed to. This can be accomplished by setting kernel parameters on capable machines in MAAS, tagging them and using these tags as constraints in the model.
-
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: nova
Username used to access rabbitmq queue.
-
rabbit-vhost | string
Default: openstack
Rabbitmq vhost.
-
rbd-client-cache | string
Enable/disable rbd client cache. Leaving this value unset will result in default Ceph rbd client settings being used (rbd cache is enabled by default for Ceph >= Giant). Supported values here are "enabled" or "disabled".
-
rbd-pool | string
Default: nova
RBD pool to use with Nova libvirt RBDImageBackend. Only required when you have libvirt-image-backend set to 'rbd'.
-
reserved-host-memory | int
Default: 512
Amount of memory in MB to reserve for the host. Defaults to 512MB.
-
restrict-ceph-pools | boolean
Optionally restrict Ceph key permissions to access pools as required.
-
resume-guests-state-on-host-boot | boolean
This option determines whether to start guests that were running before the host rebooted.
-
sysctl | string
YAML formatted associative array of sysctl values, e.g.: '{ kernel.pid_max : 4194303 }'
-
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-multipath | boolean
Use a multipath connection for iSCSI volumes. Enabling this feature causes libvirt to discover and login to available iscsi targets before presenting the disk via device mapper (/dev/mapper/XX) to the VM instead of a single path (/dev/disk/by-path/XX). If changed after deployment, each VM will require a full stop/start for changes to take affect.
-
use-syslog | boolean
Setting this to True will allow supporting services to log to syslog.
-
vcpu-pin-set | string
Sets vcpu_pin_set option in nova.conf which defines which pcpus that instance vcpus can or cannot use. For example '^0,^2' to reserve two cpus for the host.
-
verbose | boolean
Enable verbose logging.
-
virt-type | string
Default: kvm
Virtualisation flavor. Supported and tested flavors are: kvm, lxd. If using the lxd flavor, the lxd subordinate charm must also be related. Other native libvirt flavors available to exercise (dev/test only): uml, lxc, qemu. NOTE: Changing virtualisation flavor after deployment is not supported.
-
worker-multiplier | float
The CPU core multiplier to use when configuring worker processes for this services e.g. metadata-api. By default, the number of workers for each daemon is set to twice the number of CPU cores a service unit has. When deployed in a LXD container, this default value will be capped to 4 workers unless this configuration option is set.