Advertisement
Guest User

Untitled

a guest
Mar 3rd, 2017
120
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.51 KB | None | 0 0
  1. ####################
  2. # Networking options
  3. ####################
  4. # This interface is what all your api services will be bound to by default.
  5. # Additionally, all vxlan/tunnel and storage network traffic will go over this
  6. # interface by default. This interface must contain an IPv4 address.
  7. # It is possible for hosts to have non-matching names of interfaces - these can
  8. # be set in an inventory file per host or per group or stored separately, see
  9. # http://docs.ansible.com/ansible/intro_inventory.html
  10. # Yet another way to workaround the naming problem is to create a bond for the
  11. # interface on all hosts and give the bond name here. Similar strategy can be
  12. # followed for other types of interfaces.
  13. network_interface: "enp6s0f0"
  14.  
  15. # These can be adjusted for even more customization. The default is the same as
  16. # the 'network_interface'. These interfaces must contain an IPv4 address.
  17. #kolla_external_vip_interface: "{{ network_interface }}"
  18. #api_interface: "{{ network_interface }}"
  19. #storage_interface: "{{ network_interface }}"
  20. #cluster_interface: "{{ network_interface }}"
  21. #tunnel_interface: "{{ network_interface }}"
  22.  
  23. # This is the raw interface given to neutron as its external network port. Even
  24. # though an IP address can exist on this interface, it will be unusable in most
  25. # configurations. It is recommended this interface not be configured with any IP
  26. # addresses for that reason.
  27. #neutron_external_interface: "eth1"
  28.  
  29. # Valid options are [ openvswitch, linuxbridge ]
  30. #neutron_plugin_agent: "openvswitch"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement