Advertisement
Guest User

globals.yml

a guest
Aug 25th, 2016
181
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.50 KB | None | 0 0
  1. ---
  2. # You can use this file to override _any_ variable throughout Kolla.
  3. # Additional options can be found in the 'kolla/group_vars/all.yml' file.
  4.  
  5. ###################
  6. # Kolla options
  7. ###################
  8. # Valid options are [ COPY_ONCE, COPY_ALWAYS ]
  9. #config_strategy: "COPY_ALWAYS"
  10.  
  11. # Valid options are [ centos, fedora, oraclelinux, ubuntu ]
  12. kolla_base_distro: "ubuntu"
  13.  
  14. # Valid options are [ binary, source ]
  15. kolla_install_type: "source"
  16.  
  17. # This should be a VIP, an unused IP on your network that will float between
  18. # the hosts running keepalived for high-availability. When running an All-In-One
  19. # without haproxy and keepalived, this should be the first IP on your
  20. # 'network_interface' as set in the Networking section below.
  21. kolla_internal_vip_address: "172.16.2.203"
  22.  
  23. # This is the DNS name that maps to the kolla_internal_vip_address VIP. By
  24. # default it is the same as kolla_internal_vip_address.
  25. #kolla_internal_fqdn: "{{ kolla_internal_vip_address }}"
  26.  
  27. # This should be a VIP, an unused IP on your network that will float between
  28. # the hosts running keepalived for high-availability. It defaults to the
  29. # kolla_internal_vip_address, allowing internal and external communication to
  30. # share the same address. Specify a kolla_external_vip_address to separate
  31. # internal and external requests between two VIPs.
  32. #kolla_external_vip_address: "{{ kolla_internal_vip_address }}"
  33.  
  34. # The Public address used to communicate with OpenStack as set in the public_url
  35. # for the endpoints that will be created. This DNS name should map to
  36. # kolla_external_vip_address.
  37. #kolla_external_fqdn: "{{ kolla_external_vip_address }}"
  38.  
  39. ####################
  40. # Docker options
  41. ####################
  42. ### Example: Private repository with authentication
  43. #
  44. docker_registry: "172.16.2.241:4000"
  45. # docker_namespace: "companyname"
  46. # docker_registry_username: "sam"
  47. # docker_registry_password: "correcthorsebatterystaple"
  48.  
  49.  
  50. ####################
  51. # Networking options
  52. ####################
  53. # This interface is what all your api services will be bound to by default.
  54. # Additionally, all vxlan/tunnel and storage network traffic will go over this
  55. # interface by default. This interface must contain an IPv4 address.
  56. network_interface: "eth0"
  57.  
  58. # These can be adjusted for even more customization. The default is the same as
  59. # the 'network_interface'. These interfaces must container an IPv4 address.
  60. #kolla_external_vip_interface: "{{ network_interface }}"
  61. #api_interface: "{{ network_interface }}"
  62. #storage_interface: "{{ network_interface }}"
  63. #tunnel_interface: "{{ network_interface }}"
  64.  
  65. # This is the raw interface given to neutron as its external network port. Even
  66. # though an IP address can exist on this interface, it will be unusable in most
  67. # configurations. It is recommended this interface not be configured with any IP
  68. # addresses for that reason.
  69. neutron_external_interface: "p787p1"
  70.  
  71. # Valid options are [ openvswitch, linuxbridge ]
  72. neutron_plugin_agent: "openvswitch"
  73.  
  74.  
  75. ####################
  76. # TLS options
  77. ####################
  78. # To provide encryption and authentication on the kolla_external_vip_interface,
  79. # TLS can be enabled. When TLS is enabled, certificates must be provided to
  80. # allow clients to perform authentication. The default is TLS disabled.
  81. # kolla_enable_tls_external: "yes"
  82. # kolla_external_fqdn_cert: "{{ node_config_directory }}/certificates/haproxy.pem"
  83.  
  84.  
  85. ####################
  86. # OpenStack options
  87. ####################
  88. # Use these options to set the various log levels across all OpenStack projects
  89. openstack_logging_debug: "True"
  90.  
  91. # Valid options are [ novnc, spice ]
  92. #nova_console: "novnc"
  93.  
  94. # OpenStack services can be enabled or disabled with these options
  95. enable_central_logging: "yes"
  96. #enable_ceph: "no"
  97. #enable_ceph_rgw: "no"
  98. enable_cinder: "yes"
  99. #enable_heat: "yes"
  100. #enable_horizon: "yes"
  101. #enable_ironic: "no"
  102. #enable_magnum: "no"
  103. #enable_manila: "no"
  104. #enable_mistral: "no"
  105. #enable_mongodb: "no"
  106. #enable_murano: "no"
  107. #enable_swift: "no"
  108. #enable_heat: "no"
  109.  
  110.  
  111. ###################
  112. # Ceph options
  113. ###################
  114. # Ceph can be setup with a caching to improve performance. To use the cache you
  115. # must provide separate disks than those for the OSDs
  116. # ceph_use_cache: "no"
  117. # Valid options are [ forward, none, writeback ]
  118. # ceph_cache_mode: "writeback"
  119.  
  120. # A requirement for using the erasure-coded pools is you must setup a cache tier
  121. # Valid options are [ erasure, replicated ]
  122. # ceph_pool_type: "replicated"
  123.  
  124.  
  125. #######################################
  126. # Manila - Shared File Systems Options
  127. #######################################
  128. #manila_enable_dhss: "yes"
  129.  
  130.  
  131. ##################################
  132. # Swift - Object Storage Options
  133. ##################################
  134. # Swift expects block devices to be available for storage. Two types of storage
  135. # are supported: 1 - storage device with a special partition name and filesystem
  136. # label, 2 - unpartitioned disk with a filesystem. The label of this filesystem
  137. # is used to detect the disk which Swift will be using.
  138.  
  139. # Swift support two mathcing modes, valid options are [ prefix, strict ]
  140. #swift_devices_match_mode: "strict"
  141.  
  142. # This parameter defines matching pattern: if "strict" mode was selected,
  143. # for swift_devices_match_mode then swift_device_name should specify the name of
  144. # the special swift partition for example: "KOLLA_SWIFT_DATA", if "prefix" mode was
  145. # selected then swift_devices_name should specify a pattern which would match to
  146. # filesystems' labels prepared for swift.
  147. #swift_devices_name: "KOLLA_SWIFT_DATA"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement