Takashi Kajinami 2ffc7aedf4 Re-organize service definitions
None of supported operating systems have separate ovsdb-service, so
the logic to enable that separate service is unused and useless.

Also current definition of status and hasstatus are just redundant and
can be removed.

Change-Id: I361e55f144b4852f76c00b8dab26c4cec37b29c1
2023-06-19 13:32:22 +09:00

26 lines
774 B
Puppet

# vswitch params
#
class vswitch::params {
include openstacklib::defaults
case $facts['os']['family'] {
'Redhat': {
$ovs_package_name = 'openvswitch'
# OVS2.5 in Red Hat family is unified package which will support plain
# OVS and also DPDK (if enabled at runtime).
$ovs_dpdk_package_name = 'openvswitch'
$ovs_service_name = 'openvswitch'
$provider = 'ovs'
}
'Debian': {
$ovs_package_name = 'openvswitch-switch'
$ovs_dpdk_package_name = 'openvswitch-switch-dpdk'
$ovs_service_name = 'openvswitch-switch'
$provider = 'ovs'
}
default: {
fail " Osfamily ${facts['os']['family']} not supported yet"
}
} # Case $facts['os']['family']
}