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
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
|
========================================================================
OPNFV Release Notes for the Fraser release of OPNFV Apex deployment tool
========================================================================
Abstract
========
This document provides the release notes for Fraser release with the Apex
deployment toolchain.
License
=======
All Apex and "common" entities are protected by the Apache 2.0 License
( http://www.apache.org/licenses/ )
Important Notes
===============
This is the OPNFV Fraser release that implements the deploy stage of the
OPNFV CI pipeline via Apex.
Apex is based on RDO's Triple-O installation tool chain.
More information at http://rdoproject.org
Carefully follow the installation-instructions which guide a user on how to
deploy OPNFV using Apex installer.
Summary
=======
Fraser release with the Apex deployment toolchain will establish an OPNFV
target system on a Pharos compliant lab infrastructure. The current definition
of an OPNFV target system is OpenStack Pike combined with an SDN
controller, such as OpenDaylight. The system is deployed with OpenStack High
Availability (HA) for most OpenStack services. SDN controllers are deployed
on every controller unless deploying with one the HA FD.IO scenarios. Ceph
storage is used as Cinder backend, and is the only supported storage for
Fraser. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller
node in an HA setup. Apex also supports non-HA deployments, which deploys a
single controller and n number of compute nodes. Furthermore, Apex is
capable of deploying scenarios in a bare metal or virtual fashion. Virtual
deployments use multiple VMs on the Jump Host and internal networking to
simulate the a bare metal deployment.
- Documentation is built by Jenkins
- .iso image is built by Jenkins
- .rpm packages are built by Jenkins
- Jenkins deploys a Fraser release with the Apex deployment toolchain
bare metal, which includes 3 control+network nodes, and 2 compute nodes.
Release Data
============
+--------------------------------------+--------------------------------------+
| **Project** | apex |
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | opnfv-6.0.0 |
| | |
+--------------------------------------+--------------------------------------+
| **Release designation** | 6.0.0 |
| | |
+--------------------------------------+--------------------------------------+
| **Release date** | 2018-04-30 |
| | |
+--------------------------------------+--------------------------------------+
| **Purpose of the delivery** | OPNFV Fraser release |
| | |
+--------------------------------------+--------------------------------------+
Version change
--------------
Module version changes
~~~~~~~~~~~~~~~~~~~~~~
This is the first tracked version of the Fraser release with the Apex
deployment toolchain. It is based on following upstream versions:
- OpenStack (Pike release)
- OpenDaylight (Nitrogen/Oxygen releases)
- CentOS 7
Document Version Changes
~~~~~~~~~~~~~~~~~~~~~~~~
This is the first tracked version of Fraser release with the Apex
deployment toolchain.
The following documentation is provided with this release:
- OPNFV Installation instructions for the Fraser release with the Apex
deployment toolchain - ver. 1.0.0
- OPNFV Release Notes for the Fraser release with the Apex deployment
toolchain - ver. 1.0.0 (this document)
Deliverables
------------
Software Deliverables
~~~~~~~~~~~~~~~~~~~~~
- Apex .iso file
- Apex release .rpm (opnfv-apex-release)
- Apex overcloud .rpm (opnfv-apex) - For nosdn and OpenDaylight Scenarios
- Apex undercloud .rpm (opnfv-apex-undercloud)
- Apex common .rpm (opnfv-apex-common)
- build.py - Builds the above artifacts
- opnfv-deploy - Automatically deploys Target OPNFV System
- opnfv-clean - Automatically resets a Target OPNFV Deployment
- opnfv-util - Utility to connect to or debug Overcloud nodes + OpenDaylight
Documentation Deliverables
~~~~~~~~~~~~~~~~~~~~~~~~~~
- OPNFV Installation instructions for the Fraser release with the Apex
deployment toolchain - ver. 6.0
- OPNFV Release Notes for the Fraser release with the Apex deployment
toolchain - ver. 6.0 (this document)
Known Limitations, Issues and Workarounds
=========================================
System Limitations
------------------
**Max number of blades:** 1 Apex undercloud, 3 Controllers, 20 Compute blades
**Min number of blades:** 1 Apex undercloud, 1 Controller, 1 Compute blade
**Storage:** Ceph is the only supported storage configuration.
**Min master requirements:** At least 16GB of RAM for baremetal Jump Host,
24GB for virtual deployments (noHA).
Known Issues
------------
**JIRA TICKETS:**
+--------------------------------------+--------------------------------------+
| **JIRA REFERENCE** | **SLOGAN** |
| | |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-280 | Deleted network not cleaned up |
| | on controller |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-295 | Missing support for VLAN tenant |
| | networks |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-368 | Ceilometer stores samples and events |
| | forever |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-371 | Ceph partitions need to be prepared |
| | on deployment when using 2nd disk |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-375 | Default glance storage points to |
| | http,swift when ceph disabled |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-389 | Compute kernel parameters are used |
| | for all nodes |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-412 | Install failures with UEFI |
+--------------------------------------+--------------------------------------+
| JIRA: APEX-425 | Need to tweak performance settings |
| | virtual DPDK scenarios |
+--------------------------------------+--------------------------------------+
Workarounds
-----------
**-**
Test Result
===========
Please reference Functest project documentation for test results with the
Apex installer.
References
==========
For more information on the OPNFV Fraser release, please see:
http://wiki.opnfv.org/releases/Fraser
:Authors: Tim Rozet (trozet@redhat.com)
:Authors: Dan Radez (dradez@redhat.com)
:Version: 6.0
|
