X-Git-Url: https://osm.etsi.org/gitweb/?a=blobdiff_plain;f=openvimd.cfg;h=9641938c1b37354d849ba2c33da3a05afb3ce66a;hb=refs%2Fchanges%2F17%2F1317%2F3;hp=bfa937ac3584a56a26ad07972596e554c37b37f4;hpb=7256d6b4cac032784adb1b7cb30699bd753e2b3c;p=osm%2Fopenvim.git diff --git a/openvimd.cfg b/openvimd.cfg index bfa937a..9641938 100644 --- a/openvimd.cfg +++ b/openvimd.cfg @@ -35,7 +35,7 @@ mode: test #Openflow controller information -of_controller: floodlight # Type of controller to be used. +of_controller: floodlight # Type of controller to be used. # Valid controllers are 'opendaylight', 'floodlight' or #of_controller_module: module # Only needed for . Python module that implement # this controller. By default a file with the name .py is used @@ -51,12 +51,12 @@ of_controller_dpid: '00:01:02:03:04:05:06:07' # Openflow Switch identifier (p 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: 0.0.0.0 # 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 @@ -72,14 +72,18 @@ 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 +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 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: