of_controller_nets_with_same_vlan: false # (by default, true)
#Server parameters
-http_host: localhost # IP address where openvim is listening (by default, localhost)
+http_host: 0.0.0.0 # IP address where openvim is listening (by default, localhost)
http_port: 9080 # General port where openvim is listening (by default, 9080)
http_admin_port: 9085 # Admin port where openvim is listening (when missing, no administration server is launched)
#database parameters
-db_host: localhost # by default localhost
+db_host: localhost # by default localhost
db_user: vim # DB user
db_passwd: vimpw # DB password
db_name: vim_db # Name of the VIM DB
network_vlan_range_start: 3000
network_vlan_range_end: 4000
+# Overlay network implementation. Options are:
+# - ovs : (by default) Use a vlxan mesh between computes to handle the network overlay.
+# - bridge: Use pre-populated linux bridges with L2 conectivity at compte nodes.
+network_type : ovs
+ovs_controller_ip : localhost # dhcp controller IP address, must be change in order to
+ovs_controller_user : "osm_dhcp" # User for the dchp controller for OVS networks
+ovs_controller_file_path : "/var/lib/openvim" # Path for dhcp daemon configuration, by default '/var/lib/openvim'
+
+
#host bridge interfaces for networks
-# Openvim cannot create bridge networks automatically, in the same way as other CMS do.
+# Apply only for 'network_type: bridge'
+# Indicates the bridges at compute nodes to be used for the overlay networks
# Bridge networks need to be pre-provisioned on each host and Openvim uses those pre-provisioned bridge networks.
# Openvim assumes that the following bridge interfaces have been created on each host, appropriately associated to a physical port.
# The following information needs to be provided:
# - The speed of the physical port in Gbps, where that bridge interface was created
# For instance, next example assumes that 10 bridges have been created on each host
# using vlans 2001 to 2010, associated to a 1Gbps physical port
-bridge_ifaces:
- #name: [vlan, speed in Gbps]
- virbrMan1: [2001, 1]
- virbrMan2: [2002, 1]
- virbrMan3: [2003, 1]
- virbrMan4: [2004, 1]
- virbrMan5: [2005, 1]
- virbrMan6: [2006, 1]
- virbrMan7: [2007, 1]
- virbrMan8: [2008, 1]
- virbrMan9: [2009, 1]
- virbrMan10: [2010, 1]
+#bridge_ifaces:
+# #name: [vlan, speed in Gbps]
+# virbrMan1: [2001, 1]
+# virbrMan2: [2002, 1]
+# virbrMan3: [2003, 1]
+# virbrMan4: [2004, 1]
+# virbrMan5: [2005, 1]
+# virbrMan6: [2006, 1]
+# virbrMan7: [2007, 1]
+# virbrMan8: [2008, 1]
+# virbrMan9: [2009, 1]
+# virbrMan10: [2010, 1]
#Used only when 'mode' is at development'. Indicates which 'bridge_ifaces' is used for dataplane networks
-development_bridge: virbrMan10
+#development_bridge: virbrMan10
#DHCP SERVER PARAMETERS.
#In case some of the previous 'bridge_ifaces' are connected to an EXTERNAL dhcp server, provide
# the server parameters to allow openvim getting the allocated IP addresses of virtual machines
# connected to the indicated 'bridge_ifaces' and or 'nets'. Openvim will connect to the dhcp server by ssh.
-#DHCP server must contain a shell script "./get_dhcp_lease.sh" that accept a mac address as parameter
-# and return empty or the allocated IP address. See an example at the end of the file ./openvim/dhcp_thread.py
+#DHCP server must contain a shell script "get_dhcp_lease.sh" included in the path, that accepts a mac address as
+# parameter and return empty or the allocated IP address. See an example at the end of the file
+# ./openvim/dhcp_thread.py
#COMMENT all lines in case you do not have a DHCP server in 'normal', 'development' or 'host only' modes.
# For 'test' or 'OF only' modes you can leave then uncommented, because in these modes fake IP
# address are generated instead of connecting with a real DHCP server.
log_level: ERROR
log_level_db: DEBUG
log_level_of: DEBUG
+
+