Advertisement
Guest User

globals.yml

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