Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ###################
- # Kolla options
- ###################
- #config_strategy: "COPY_ALWAYS"
- node_custom_config: "/etc/kolla/config"
- kolla_base_distro: "centos"
- kolla_install_type: "binary"
- openstack_release: "2.0.2"
- kolla_internal_vip_address: "192.168.0.100"
- kolla_internal_fqdn: "controller.hcm.vt"
- #kolla_external_vip_address: "{{ kolla_internal_vip_address }}"
- #kolla_external_fqdn: "{{ kolla_external_vip_address }}"
- ####################
- # Docker options
- ####################
- docker_registry: "192.168.0.3:4000"
- #docker_namespace: "companyname"
- #docker_registry_username: "sam"
- #docker_registry_password: "correcthorsebatterystaple"
- ####################
- # Networking options
- ####################
- network_interface: "bond0.3"
- #kolla_external_vip_interface: "{{ network_interface }}"
- api_interface: "bond0.3"
- storage_interface: "bond0.3"
- cluster_interface: "bond1.4"
- tunnel_interface: "bond0.3"
- neutron_external_interface: "bond0.158"
- # Valid options are [ openvswitch, linuxbridge ]
- neutron_plugin_agent: "linuxbridge"
- ####################
- # keepalived options
- ####################
- # Arbitary unique number from 0..255
- #keepalived_virtual_router_id: "51"
- ####################
- # TLS options
- ####################
- # To provide encryption and authentication on the kolla_external_vip_interface,
- # TLS can be enabled. When TLS is enabled, certificates must be provided to
- # allow clients to perform authentication.
- #kolla_enable_tls_external: "no"
- #kolla_external_fqdn_cert: "{{ node_config_directory }}/certificates/haproxy.pem"
- ####################
- # OpenStack options
- ####################
- # Use these options to set the various log levels across all OpenStack projects
- # Valid options are [ True, False ]
- #openstack_logging_debug: "False"
- # Valid options are [ novnc, spice ]
- #nova_console: "novnc"
- # OpenStack services can be enabled or disabled with these options
- enable_central_logging: "no"
- enable_ceph: "yes"
- enable_ceph_rgw: "no"
- enable_cinder: "yes"
- enable_heat: "yes"
- enable_horizon: "yes"
- enable_ironic: "no"
- enable_magnum: "no"
- enable_manila: "no"
- enable_mistral: "no"
- enable_mongodb: "no"
- enable_murano: "no"
- enable_swift: "no"
- ###################
- # Ceph options
- ###################
- # Ceph can be setup with a caching to improve performance. To use the cache you
- # must provide separate disks than those for the OSDs
- #ceph_enable_cache: "no"
- # Valid options are [ forward, none, writeback ]
- #ceph_cache_mode: "writeback"
- # A requirement for using the erasure-coded pools is you must setup a cache tier
- # Valid options are [ erasure, replicated ]
- #ceph_pool_type: "replicated"
- #######################################
- # Manila - Shared File Systems Options
- #######################################
- #manila_enable_dhss: "yes"
- ##################################
- # Swift - Object Storage Options
- ##################################
- # Swift expects block devices to be available for storage. Two types of storage
- # are supported: 1 - storage device with a special partition name and filesystem
- # label, 2 - unpartitioned disk with a filesystem. The label of this filesystem
- # is used to detect the disk which Swift will be using.
- # Swift support two mathcing modes, valid options are [ prefix, strict ]
- #swift_devices_match_mode: "strict"
- # This parameter defines matching pattern: if "strict" mode was selected,
- # for swift_devices_match_mode then swift_device_name should specify the name of
- # the special swift partition for example: "KOLLA_SWIFT_DATA", if "prefix" mode was
- # selected then swift_devices_name should specify a pattern which would match to
- # filesystems' labels prepared for swift.
- #swift_devices_name: "KOLLA_SWIFT_DATA"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement