Oil Charms Nova Hyperv
- By OIL Charms
- Cloud
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 0 | 19 Mar 2021 |
juju deploy oil-charms-nova-hyperv
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
ad-computer-group | string
Default: Nova
Computer group that will be joined after adding AD relation
-
ad-user | string
Default: nova-hyperv
User that will created after adding AD relation
-
bond-name | string
Default: bond0
The name of the bond interface
-
bond-ports | string
MAC addresses of ports participating in bond link. A new Net-LbfoTeam called bond0 will be created in LACP mode. This interface can be used as a data-port.
-
data-port | string
Ethernet inerface to use for vmswitch. This can be a MAC address or an interface name. This option is mandatory if more then one interface is present on the target system. In cases where there is only one interface on the system, the vmswitch will be created using that interface and OSManagement will be set to True, regardless of the vmswitch-management option. Avoid using the management interface as a data interface where system has more then one NIC. If you would like to use bonding, make sure you supply valid MAC addresses in the bond-ports config field, and use "bond0" as a data-port name.
-
debug | boolean
Enable debug logging
-
enable-cluster-driver | boolean
Default: False
Enables the Hyper-V compute driver for clustering. This requires at least two Hyper-V compute joined to a cluster. NOTE: Available only in releases >= Mitaka
-
installer-url | string
overwrite default installer location. Take care to set the correct openstack-version as that will be used by the charm to pick the correct config templates. If you use this option, you may enable file integrity checking by specifying an md5sum at the end of the URL as follows: https://example.com/installer.msi#md5=<hash>
-
instances-dir | string
Default: C:/OpenStack/Instances
Location in which to store VM disks
-
log-dir | string
Default: C:/OpenStack/Log
Log folder location
-
monitors | string
Yaml with the additional checks to be set on 'local-monitors' relation with NSClient++
-
network-type | string
Default: hyperv
Neutron agent to use. Valid options are: * hyperv * ovs Default is hyperv. Note: ovs is available for Kilo and above
-
openstack-origin | string
Default: liberty
Version of Openstack nova compute to install. Choices are: - juno - kilo - liberty
-
openstack-version | string
Default: liberty
Version of Openstack nova compute to install. This option overrides openstack-origin. Choices are: - juno - kilo - liberty
-
os-data-network | string
The IP address and netmask of the OpenStack Data network (e.g., 192.168.0.0/24) . This network will be used for tenant network traffic in overlay networks. NOTE: If ovs is selected as the network type, this option overrides data-port. OVS on Windows requires that the os data network be set on the vmswitch itself. That means that if an interface has an IP in the os-data-network range, that interface will be added to the vmswitch. There is a caveat here. If os-data-network is on a different interface then data-port, it might result in the hyper-v compute nodes not being able to use VLAN network segregation.
-
ovs-installer-url | string
Default: https://www.cloudbase.it/downloads/openvswitch-hyperv-installer-beta.msi
Location of the OVS MSI installer
-
rabbit-user | string
Default: nova
Username used to access rabbitmq queue
-
rabbit-vhost | string
Default: openstack
Rabbitmq vhost
-
verbose | boolean
Enable verbose logging
-
vmswitch-management | boolean
Allow management OS on this vm switch. If True, the switch will be set in DHCP mode.
-
vmswitch-name | string
Default: br100
Virtual switch to use