X-Git-Url: https://osm.etsi.org/gitweb/?a=blobdiff_plain;f=openvimd.cfg;h=545b739383211b29e004b8b1357879ddcbf63238;hb=refs%2Fchanges%2F59%2F1059%2F1;hp=bfa937ac3584a56a26ad07972596e554c37b37f4;hpb=d2ba19b5f2b37a0337c47dd5634a409735cd8285;p=osm%2Fopenvim.git

diff --git a/openvimd.cfg b/openvimd.cfg
index bfa937a..545b739 100644
--- a/openvimd.cfg
+++ b/openvimd.cfg
@@ -72,14 +72,14 @@ tenant_id: fc7b43b6-6bfa-11e4-84d2-5254006d6777   # Default tenant identifier fo
 network_vlan_range_start: 3000
 network_vlan_range_end:   4000
 
-# Network overlay supported by openvim compute, bsae on openvswicth or linux bridges to manage management networks for NFVs.
-# - ovs : Create a vlxan mesh between computes to handle the network overlay, no prepopulated bridges or networks is need it.
-# - bridge: Use pre-populate linux bridges by openvim configuration scripts.
-
+# 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
 
 #host bridge interfaces for networks
-# Openvim cannot create bridge networks automatically, in the same way as other CMS do when network type is "bridge".
+# 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: