Advertisement
Guest User

Untitled

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