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
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
Daisy4nfv configuration
=======================
This document provides guidelines on how to install and configure the Euphrates
release of OPNFV when using Daisy as a deployment tool including required
software and hardware configurations.
Installation and configuration of host OS, OpenStack etc. can be supported by
Daisy on Virtual nodes and Bare Metal nodes.
The audience of this document is assumed to have good knowledge in
networking and Unix/Linux administration.
Prerequisites
-------------
Before starting the installation of the Euphrates release of OPNFV, some plannings
must be done.
Retrieve the installation iso image
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
First of all, the installation iso which includes packages of Daisy, OS,
OpenStack, and so on is needed for deploying your OPNFV environment.
The stable release iso image can be retrieved via `OPNFV software download page <https://www.opnfv.org/software>`_
The daily build iso image can be retrieved via OPNFV artifact repository:
http://artifacts.opnfv.org/daisy.html
NOTE: Search the keyword "daisy/Euphrates" to locate the iso image.
E.g.
daisy/opnfv-2017-10-06_09-50-23.iso
Download the iso file, then mount it to a specified directory and get the
opnfv-*.bin from that directory.
The git url and sha512 checksum of iso image are recorded in properties files.
According to these, the corresponding deployment scripts can be retrieved.
Retrieve the deployment scripts
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To retrieve the repository of Daisy on Jumphost use the following command:
- git clone https://gerrit.opnfv.org/gerrit/daisy
To get stable Euphrates release, you can use the following command:
- git checkout euphrates.1.0
Setup Requirements
------------------
If you have only 1 Bare Metal server, Virtual deployment is recommended. if you have more
than 3 servers, the Bare Metal deployment is recommended. The minimum number of
servers for each role in Bare metal deployment is listed below.
+------------+------------------------+
| **Role** | **Number of Servers** |
| | |
+------------+------------------------+
| Jump Host | 1 |
| | |
+------------+------------------------+
| Controller | 1 |
| | |
+------------+------------------------+
| Compute | 1 |
| | |
+------------+------------------------+
Jumphost Requirements
~~~~~~~~~~~~~~~~~~~~~
The Jumphost requirements are outlined below:
1. CentOS 7.2 (Pre-installed).
2. Root access.
3. Libvirt virtualization support(For virtual deployment).
4. Minimum 1 NIC(or 2 NICs for virtual deployment).
- PXE installation Network (Receiving PXE request from nodes and providing OS provisioning)
- IPMI Network (Nodes power control and set boot PXE first via IPMI interface)
- Internet access (For getting latest OS updates)
- External Interface(For virtual deployment, exclusively used by instance traffic to access the rest of the Internet)
5. 16 GB of RAM for a Bare Metal deployment, 64 GB of RAM for a Virtual deployment.
6. CPU cores: 32, Memory: 64 GB, Hard Disk: 500 GB, (Virtual deployment needs 1 TB Hard Disk)
Bare Metal Node Requirements
----------------------------
Bare Metal nodes require:
1. IPMI enabled on OOB interface for power control.
2. BIOS boot priority should be PXE first then local hard disk.
3. Minimum 1 NIC for Compute nodes, 2 NICs for Controller nodes.
- PXE installation Network (Broadcasting PXE request)
- IPMI Network (Receiving IPMI command from Jumphost)
- Internet access (For getting latest OS updates)
- External Interface(For virtual deployment, exclusively used by instance traffic to access the rest of the Internet)
Network Requirements
--------------------
Network requirements include:
1. No DHCP or TFTP server running on networks used by OPNFV.
2. 2-7 separate networks with connectivity between Jumphost and nodes.
- PXE installation Network
- IPMI Network
- Internet access Network
- OpenStack Public API Network
- OpenStack Private API Network
- OpenStack External Network
- OpenStack Tenant Network(currently, VxLAN only)
3. Lights out OOB network access from Jumphost with IPMI node enabled (Bare Metal deployment only).
4. Internet access Network has Internet access, meaning a gateway and DNS availability.
5. OpenStack External Network has Internet access too if you want instances to access the Internet.
Note: **All networks except OpenStack External Network can share one NIC(Default configuration) or use an exclusive**
**NIC(Reconfigurated in network.yml).**
Execution Requirements (Bare Metal Only)
----------------------------------------
In order to execute a deployment, one must gather the following information:
1. IPMI IP addresses of the nodes.
2. IPMI login information for the nodes (user/password).
|
