blob: 51deb4e28f112aeeac796cabe07a4e558f4c53ec (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
##############################################################################
# Copyright (c) 2015 Ericsson AB and others.
# jonas.bjurel@ericsson.com
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Apache License, Version 2.0
# which accompanies this distribution, and is available at
# http://www.apache.org/licenses/LICENSE-2.0
##############################################################################
############################################################################### # Description:
# This .yaml configuration file defines the configuration of the fuel
# deployment and is passed as an argument to deploy.sh
# eg. deploy.sh -c https://artifact.opnfv.org/fuel/config
# This will make build.sh fetch this configuration file and configure the
# deployment accordingly.
# After the deployment, a copy of this file gets uploaded to fuel:
# /root/deploy-config.yaml, as well as the sha-1 sum of this file:
# /root/deploy-config.sha1
##############################################################################
##############################################################################
# deployment configuration meta-data
deployment-scenario-metadata:
title: NFV OVS HA deployment
version: 0.9.0
created: Jul 12 2016
comment: Rebased to Fuel9
##############################################################################
# Stack extentions are opnfv added value features in form of a fuel-plugin
# plug-ins listed below will be enabled and configured according to the
# <module-config-base-uri>/<module-config-name>_<module-config-version>.yaml
# It does so by copying the config file to the local plugin config directory
stack-extensions:
- module: fuel-plugin-ovs
module-config-name: fuel-nshovs
module-config-version: 0.9.0
module-config-override:
metadata:
versions:
- install_dpdk:
value: true
metadata:
plugin_version: 0.9.0
##############################################################################
# By editing the override-config sections below, you can override arbitrary
# configuration name-space settings
dea-override-config:
fuel:
FEATURE_GROUPS:
- experimental
environment:
net_segment_type: vlan
nodes:
- id: 1
interfaces: interfaces_vlan
role: controller
- id: 2
interfaces: interfaces_vlan
role: mongo,controller
- id: 3
interfaces: interfaces_vlan
role: ceph-osd,controller
- id: 4
interfaces: interfaces_dpdk
role: ceph-osd,compute
attributes: attributes_1
- id: 5
interfaces: interfaces_dpdk
role: ceph-osd,compute
attributes: attributes_1
attributes_1:
hugepages:
dpdk:
value: 128
nova:
value:
'2048': 1024
network:
networking_parameters:
segmentation_type: vlan
vlan_range:
- 1000
- 1030
networks:
- cidr: null
gateway: null
ip_ranges: []
meta:
configurable: false
map_priority: 2
name: private
neutron_vlan_range: true
notation: null
render_addr_mask: null
render_type: null
seg_type: vlan
use_gateway: false
vlan_start: null
name: private
vlan_start: null
dha-override-config:
nodes:
- id: 1
libvirtName: controller1
libvirtTemplate: templates/virtual_environment/vms/controller.xml
- id: 2
libvirtName: controller2
libvirtTemplate: templates/virtual_environment/vms/controller.xml
- id: 3
libvirtName: controller3
libvirtTemplate: templates/virtual_environment/vms/controller.xml
- id: 4
libvirtName: compute1
libvirtTemplate: templates/virtual_environment/vms/compute.xml
- id: 5
libvirtName: compute2
libvirtTemplate: templates/virtual_environment/vms/compute.xml
- id: 6
libvirtName: fuel-master
libvirtTemplate: templates/virtual_environment/vms/fuel.xml
isFuel: yes
username: root
password: r00tme
##############################################################################
# The verification pipeline may populate the section below with arbitrary
# testing information, which post deploy can be retreived from the fuel master:
# /root/deploy-config.yaml
test:
|
