blob: 545b739383211b29e004b8b1357879ddcbf63238 [file] [log] [blame]
tiernof7aa8c42016-09-06 16:43:04 +02001##
2# Copyright 2015 Telefónica Investigación y Desarrollo, S.A.U.
tierno9a61c6b2016-09-08 10:57:02 +02003# This file is part of openvim
tiernof7aa8c42016-09-06 16:43:04 +02004# All Rights Reserved.
5#
6# Licensed under the Apache License, Version 2.0 (the "License"); you may
7# not use this file except in compliance with the License. You may obtain
8# a copy of the License at
9#
10# http://www.apache.org/licenses/LICENSE-2.0
11#
12# Unless required by applicable law or agreed to in writing, software
13# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
14# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
15# License for the specific language governing permissions and limitations
16# under the License.
17#
18# For those usages not covered by the Apache License, Version 2.0 please
19# contact with: nfvlabs@tid.es
20##
21
22
23
24#Miscellaneous
25#Option to test openvim without the needed infrastructure, possible values are
26# "normal" by default, Openflow controller (OFC), switch and real host are needed
27# "test" Used for testing http API and database without connecting to host or to OFC
28# "host only" Used when neither OFC nor OF switch are provided.
29# Dataplane network connection must be done manually.
30# "OF only" Used for testing of new openflow controllers support. No real VM deployments will be done but
31# OFC will be used as in real mode
32# "development" Forced a cloud-type deployment, nomal memory instead of hugepages is used,
33# without cpu pinning, and using a bridge network instead of a real OFC dataplane networks.
34# The same 'development_bridge' (see below) is used for all dataplane networks
35mode: test
36
37#Openflow controller information
38of_controller: floodlight # Type of controller to be used.
39 # Valid controllers are 'opendaylight', 'floodlight' or <custom>
40#of_controller_module: module # Only needed for <custom>. Python module that implement
41 # this controller. By default a file with the name <custom>.py is used
42#of_<other>: value # Other parameters required by <custom> controller. Consumed by __init__
43of_user: user credentials # User credentials for the controller if needed
44of_password: passwd credentials # Password credentials for the controller if needed
45of_controller_ip: 127.0.0.1 # IP address where the Openflow controller is listening
46of_controller_port: 7070 # TCP port where the Openflow controller is listening (REST API server)
47of_controller_dpid: '00:01:02:03:04:05:06:07' # Openflow Switch identifier (put here the right number)
48
49#This option is used for those openflow switch that cannot deliver one packet to several output with different vlan tags
50#When set to true, it fails when trying to attach different vlan tagged ports to the same net
51of_controller_nets_with_same_vlan: false # (by default, true)
52
53#Server parameters
54http_host: localhost # IP address where openvim is listening (by default, localhost)
55http_port: 9080 # General port where openvim is listening (by default, 9080)
56http_admin_port: 9085 # Admin port where openvim is listening (when missing, no administration server is launched)
57
58#database parameters
tierno789b61c2016-10-18 15:21:58 +000059db_host: 0.0.0.0 # by default localhost
tiernof7aa8c42016-09-06 16:43:04 +020060db_user: vim # DB user
61db_passwd: vimpw # DB password
62db_name: vim_db # Name of the VIM DB
63
64#host paremeters
65image_path: "/opt/VNF/images" # Folder, same for every host, where the VNF images will be copied
66
67#testing parameters (used by ./test/test_openvim.py)
68tenant_id: fc7b43b6-6bfa-11e4-84d2-5254006d6777 # Default tenant identifier for testing
69
70#VLAN ranges used for the dataplane networks (ptp, data)
71#When a network is created an unused value in this range is used
72network_vlan_range_start: 3000
73network_vlan_range_end: 4000
74
tierno4a8f0df2017-01-19 18:59:59 +010075# Overlay network implementation. Options are:
76# - ovs : (by default) Use a vlxan mesh between computes to handle the network overlay.
77# - bridge: Use pre-populated linux bridges with L2 conectivity at compte nodes.
Mirabal7256d6b2016-12-15 10:51:19 +000078network_type : ovs
79
tiernof7aa8c42016-09-06 16:43:04 +020080#host bridge interfaces for networks
tierno4a8f0df2017-01-19 18:59:59 +010081# Apply only for 'network_type: bridge'
82# Indicates the bridges at compute nodes to be used for the overlay networks
tiernof7aa8c42016-09-06 16:43:04 +020083# Bridge networks need to be pre-provisioned on each host and Openvim uses those pre-provisioned bridge networks.
84# Openvim assumes that the following bridge interfaces have been created on each host, appropriately associated to a physical port.
85# The following information needs to be provided:
86# - Name of the bridge (identical in all hosts)
87# - VLAN tag associated to each bridge interface
88# - The speed of the physical port in Gbps, where that bridge interface was created
89# For instance, next example assumes that 10 bridges have been created on each host
90# using vlans 2001 to 2010, associated to a 1Gbps physical port
Mirabal7256d6b2016-12-15 10:51:19 +000091#bridge_ifaces:
92# #name: [vlan, speed in Gbps]
93# virbrMan1: [2001, 1]
94# virbrMan2: [2002, 1]
95# virbrMan3: [2003, 1]
96# virbrMan4: [2004, 1]
97# virbrMan5: [2005, 1]
98# virbrMan6: [2006, 1]
99# virbrMan7: [2007, 1]
100# virbrMan8: [2008, 1]
101# virbrMan9: [2009, 1]
102# virbrMan10: [2010, 1]
tiernof7aa8c42016-09-06 16:43:04 +0200103
104#Used only when 'mode' is at development'. Indicates which 'bridge_ifaces' is used for dataplane networks
Mirabal7256d6b2016-12-15 10:51:19 +0000105#development_bridge: virbrMan10
tiernof7aa8c42016-09-06 16:43:04 +0200106
107#DHCP SERVER PARAMETERS.
108#In case some of the previous 'bridge_ifaces' are connected to an EXTERNAL dhcp server, provide
109# the server parameters to allow openvim getting the allocated IP addresses of virtual machines
110# connected to the indicated 'bridge_ifaces' and or 'nets'. Openvim will connect to the dhcp server by ssh.
Jokin Garayefc2bfb2016-11-09 13:05:53 +0100111#DHCP server must contain a shell script "get_dhcp_lease.sh" included in the path, that accepts a mac address as
112# parameter and return empty or the allocated IP address. See an example at the end of the file
113# ./openvim/dhcp_thread.py
tiernof7aa8c42016-09-06 16:43:04 +0200114#COMMENT all lines in case you do not have a DHCP server in 'normal', 'development' or 'host only' modes.
115# For 'test' or 'OF only' modes you can leave then uncommented, because in these modes fake IP
116# address are generated instead of connecting with a real DHCP server.
117dhcp_server:
118 host: host-ip-or-name
119 #port: 22 #ssh port, by default 22
120 provider: isc-dhcp-server #dhcp-server type
121 user: user
122 #provide password, or key if needed
123 password: passwd
124 #key: ssh-access-key
125 #list of the previous bridge interfaces attached to this dhcp server
126 bridge_ifaces: [ virbrMan1, virbrMan2 ]
127 #list of the networks attached to this dhcp server
128 nets: [default]
129
130
131#logging parameters # DEBUG, INFO, WARNING, ERROR, CRITICAL
132log_level: ERROR
133log_level_db: DEBUG
134log_level_of: DEBUG
Mirabal7256d6b2016-12-15 10:51:19 +0000135
136