Advertisement
Guest User

Untitled

a guest
Oct 4th, 2016
101
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.71 KB | None | 0 0
  1.  
  2. ###################
  3. # Kolla options
  4. ###################
  5.  
  6. #config_strategy: "COPY_ALWAYS"
  7.  
  8. node_custom_config: "/etc/kolla/config"
  9.  
  10. kolla_base_distro: "centos"
  11. kolla_install_type: "binary"
  12.  
  13. openstack_release: "2.0.2"
  14.  
  15. kolla_internal_vip_address: "192.168.0.100"
  16. kolla_internal_fqdn: "controller.hcm.vt"
  17.  
  18. #kolla_external_vip_address: "{{ kolla_internal_vip_address }}"
  19. #kolla_external_fqdn: "{{ kolla_external_vip_address }}"
  20.  
  21. ####################
  22. # Docker options
  23. ####################
  24.  
  25. docker_registry: "192.168.0.3:4000"
  26. #docker_namespace: "companyname"
  27. #docker_registry_username: "sam"
  28. #docker_registry_password: "correcthorsebatterystaple"
  29.  
  30. ####################
  31. # Networking options
  32. ####################
  33.  
  34. network_interface: "bond0.3"
  35. #kolla_external_vip_interface: "{{ network_interface }}"
  36. api_interface: "bond0.3"
  37. storage_interface: "bond0.3"
  38. cluster_interface: "bond1.4"
  39. tunnel_interface: "bond0.3"
  40. neutron_external_interface: "bond0.158"
  41.  
  42. # Valid options are [ openvswitch, linuxbridge ]
  43. neutron_plugin_agent: "linuxbridge"
  44.  
  45.  
  46. ####################
  47. # keepalived options
  48. ####################
  49. # Arbitary unique number from 0..255
  50. #keepalived_virtual_router_id: "51"
  51.  
  52.  
  53. ####################
  54. # TLS options
  55. ####################
  56. # To provide encryption and authentication on the kolla_external_vip_interface,
  57. # TLS can be enabled. When TLS is enabled, certificates must be provided to
  58. # allow clients to perform authentication.
  59. #kolla_enable_tls_external: "no"
  60. #kolla_external_fqdn_cert: "{{ node_config_directory }}/certificates/haproxy.pem"
  61.  
  62.  
  63. ####################
  64. # OpenStack options
  65. ####################
  66. # Use these options to set the various log levels across all OpenStack projects
  67. # Valid options are [ True, False ]
  68. #openstack_logging_debug: "False"
  69.  
  70. # Valid options are [ novnc, spice ]
  71. #nova_console: "novnc"
  72.  
  73. # OpenStack services can be enabled or disabled with these options
  74. enable_central_logging: "no"
  75. enable_ceph: "yes"
  76. enable_ceph_rgw: "no"
  77. enable_cinder: "yes"
  78. enable_heat: "yes"
  79. enable_horizon: "yes"
  80. enable_ironic: "no"
  81. enable_magnum: "no"
  82. enable_manila: "no"
  83. enable_mistral: "no"
  84. enable_mongodb: "no"
  85. enable_murano: "no"
  86. enable_swift: "no"
  87.  
  88.  
  89. ###################
  90. # Ceph options
  91. ###################
  92. # Ceph can be setup with a caching to improve performance. To use the cache you
  93. # must provide separate disks than those for the OSDs
  94. #ceph_enable_cache: "no"
  95. # Valid options are [ forward, none, writeback ]
  96. #ceph_cache_mode: "writeback"
  97.  
  98. # A requirement for using the erasure-coded pools is you must setup a cache tier
  99. # Valid options are [ erasure, replicated ]
  100. #ceph_pool_type: "replicated"
  101.  
  102.  
  103. #######################################
  104. # Manila - Shared File Systems Options
  105. #######################################
  106. #manila_enable_dhss: "yes"
  107.  
  108.  
  109. ##################################
  110. # Swift - Object Storage Options
  111. ##################################
  112. # Swift expects block devices to be available for storage. Two types of storage
  113. # are supported: 1 - storage device with a special partition name and filesystem
  114. # label, 2 - unpartitioned disk with a filesystem. The label of this filesystem
  115. # is used to detect the disk which Swift will be using.
  116.  
  117. # Swift support two mathcing modes, valid options are [ prefix, strict ]
  118. #swift_devices_match_mode: "strict"
  119.  
  120. # This parameter defines matching pattern: if "strict" mode was selected,
  121. # for swift_devices_match_mode then swift_device_name should specify the name of
  122. # the special swift partition for example: "KOLLA_SWIFT_DATA", if "prefix" mode was
  123. # selected then swift_devices_name should specify a pattern which would match to
  124. # filesystems' labels prepared for swift.
  125. #swift_devices_name: "KOLLA_SWIFT_DATA"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement