1 ==============================================================================
2 OPNFV Release Notes for the Colorado 3.0 release of OPNFV Apex deployment tool
3 ==============================================================================
6 .. contents:: Table of Contents
13 This document provides the release notes for Colorado 3.0 release with the Apex
19 All Apex and "common" entities are protected by the Apache License
20 ( http://www.apache.org/licenses/ )
27 +-------------+-----------+-----------------+----------------------+
28 | **Date** | **Ver.** | **Authors** | **Comment** |
30 +-------------+-----------+-----------------+----------------------+
31 | 2016-12-05 | 2.3.0 | Tim Rozet | More updates for |
32 | | | | Colorado 3.0 |
33 +-------------+-----------+-----------------+----------------------+
34 | 2016-10-26 | 2.2.0 | Tim Rozet | More updates for |
35 | | | | Colorado 2.0 |
36 +-------------+-----------+-----------------+----------------------+
37 | 2016-09-20 | 2.1.0 | Tim Rozet | More updates for |
39 +-------------+-----------+-----------------+----------------------+
40 | 2016-08-11 | 2.0.0 | Dan Radez | Updates for Colorado |
41 +-------------+-----------+-----------------+----------------------+
42 | 2015-09-17 | 1.0.0 | Dan Radez | Rewritten for |
43 | | | | RDO Manager update |
44 +-------------+-----------+-----------------+----------------------+
49 This is the OPNFV Colorado 3.0 release that implements the deploy stage of the
50 OPNFV CI pipeline via Apex.
52 Apex is based on RDO's Triple-O installation tool chain.
53 More information at http://rdoproject.org
55 Carefully follow the installation-instructions which guide a user on how to
56 deploy OPNFV using Apex installer.
61 Colorado release with the Apex deployment toolchain will establish an OPNFV
62 target system on a Pharos compliant lab infrastructure. The current definition
63 of an OPNFV target system is OpenStack Mitaka combined with an SDN
64 controller, such as OpenDaylight. The system is deployed with OpenStack High
65 Availability (HA) for most OpenStack services. SDN controllers are deployed
66 only on the first controller (see HAIssues_ for known HA SDN issues). Ceph
67 storage is used as Cinder backend, and is the only supported storage for
68 Colorado. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller
69 node in an HA setup. Apex also supports non-HA deployments, which deploys a
70 single controller and n number of compute nodes. Furthermore, Apex is
71 capable of deploying scenarios in a bare metal or virtual fashion. Virtual
72 deployments use multiple VMs on the jump host and internal networking to
73 simulate the a bare metal deployment.
75 - Documentation is built by Jenkins
76 - .iso image is built by Jenkins
77 - .rpm packages are built by Jenkins
78 - Jenkins deploys a Colorado release with the Apex deployment toolchain
79 bare metal, which includes 3 control+network nodes, and 2 compute nodes.
84 +--------------------------------------+--------------------------------------+
85 | **Project** | apex |
87 +--------------------------------------+--------------------------------------+
88 | **Repo/tag** | apex/colorado.3.0 |
90 +--------------------------------------+--------------------------------------+
91 | **Release designation** | colorado.3.0 |
93 +--------------------------------------+--------------------------------------+
94 | **Release date** | 2016-12-5 |
96 +--------------------------------------+--------------------------------------+
97 | **Purpose of the delivery** | OPNFV Colorado 3.0 release |
99 +--------------------------------------+--------------------------------------+
104 Module version changes
105 ~~~~~~~~~~~~~~~~~~~~~~
106 This is the second tracked version of the Colorado release with the Apex
107 deployment toolchain. It is based on following upstream versions:
109 - OpenStack (Mitaka release)
111 - OpenDaylight (Beryllium/Boron releases)
115 Document Version Changes
116 ~~~~~~~~~~~~~~~~~~~~~~~~
118 The following documentation is provided with this release:
120 - OPNFV Installation instructions for the Colorado release with the Apex
121 deployment toolchain - ver. 3.0
122 - OPNFV Release Notes for the Colorado release with the Apex deployment
123 toolchain - ver. 2.3.0 (this document)
128 +--------------------------------------+--------------------------------------+
129 | **JIRA REFERENCE** | **SLOGAN** |
131 +--------------------------------------+--------------------------------------+
132 | JIRA: APEX-107 | OpenDaylight HA - OVSDB Clustering |
133 +--------------------------------------+--------------------------------------+
134 | JIRA: APEX-108 | Migrate to OpenStack Mitaka |
135 +--------------------------------------+--------------------------------------+
136 | JIRA: APEX-30 | Support VLAN tagged deployments |
137 +--------------------------------------+--------------------------------------+
138 | JIRA: APEX-105 | Enable Huge Page Configuration |
140 +--------------------------------------+--------------------------------------+
141 | JIRA: APEX-111 | Allow RAM to be specified for |
142 | | Control/Compute in Virtual |
144 +--------------------------------------+--------------------------------------+
145 | JIRA: APEX-119 | Enable OVS DPDK as a deployment |
146 | | Scenario in Apex |
147 +--------------------------------------+--------------------------------------+
148 | JIRA: APEX-126 | Tacker Service deployed by Apex |
149 +--------------------------------------+--------------------------------------+
150 | JIRA: APEX-135 | Congress Service deployed by Apex |
151 +--------------------------------------+--------------------------------------+
152 | JIRA: APEX-127 | Nova Instance CPU Pinning |
153 +--------------------------------------+--------------------------------------+
154 | JIRA: APEX-130 | IPv6 Underlay Deployment |
155 +--------------------------------------+--------------------------------------+
156 | JIRA: APEX-133 | FDIO with Honeycomb Agent |
157 +--------------------------------------+--------------------------------------+
158 | JIRA: APEX-141 | Integrate VSPERF into Apex |
159 +--------------------------------------+--------------------------------------+
160 | JIRA: APEX-172 | Enable ONOS SFC |
161 +--------------------------------------+--------------------------------------+
168 +--------------------------------------+--------------------------------------+
169 | **JIRA REFERENCE** | **SLOGAN** |
171 +--------------------------------------+--------------------------------------+
172 | JIRA: APEX-86 | Need ability to specify number of |
174 +--------------------------------------+--------------------------------------+
175 | JIRA: APEX-180 | Baremetal deployment error: Failed to|
176 | | mount root partition /dev/sda on |
178 +--------------------------------------+--------------------------------------+
179 | JIRA: APEX-161 | Heat autoscaling stack creation fails|
180 | | for non-admin users |
181 +--------------------------------------+--------------------------------------+
182 | JIRA: APEX-198 | Missing NAT iptables rule for public |
183 | | network in instack VM |
184 +--------------------------------------+--------------------------------------+
185 | JIRA: APEX-147 | Installer doesn't generate/distribute|
186 | | SSH keys between compute nodes |
187 +--------------------------------------+--------------------------------------+
188 | JIRA: APEX-109 | ONOS routes local subnet traffic to |
190 +--------------------------------------+--------------------------------------+
191 | JIRA: APEX-146 | Swift service present in available |
193 +--------------------------------------+--------------------------------------+
194 | JIRA: APEX-160 | Enable force_metadata to support |
195 | | subnets with VM as the router |
196 +--------------------------------------+--------------------------------------+
197 | JIRA: APEX-114 | OpenDaylight GUI is not available |
198 +--------------------------------------+--------------------------------------+
199 | JIRA: APEX-100 | DNS1 and DNS2 should be handled in |
201 +--------------------------------------+--------------------------------------+
202 | JIRA: APEX-100 | DNS1 and DNS2 should be handled in |
204 +--------------------------------------+--------------------------------------+
205 | JIRA: APEX-155 | NIC Metric value not used when |
207 +--------------------------------------+--------------------------------------+
208 | JIRA: APEX-136 | 2 network deployment fails |
209 +--------------------------------------+--------------------------------------+
210 | JIRA: APEX-89 | Deploy Ceph OSDs on compute nodes |
211 +--------------------------------------+--------------------------------------+
212 | JIRA: APEX-137 | added arping ass dependency for |
213 | | ONOS deployments |
214 +--------------------------------------+--------------------------------------+
215 | JIRA: APEX-121 | VM Storage deletion intermittently |
217 +--------------------------------------+--------------------------------------+
218 | JIRA: APEX-182 | Nova services not correctly deployed |
219 +--------------------------------------+--------------------------------------+
220 | JIRA: APEX-153 | brbm bridge not created in jumphost |
221 +--------------------------------------+--------------------------------------+
222 | JIRA: APEX-274 | OVS DPDK scenario does not create |
223 | | vhost user ports |
224 +--------------------------------------+--------------------------------------+
225 | JIRA: APEX-277 | ONOS fails to launch due to OVS and |
226 | | Kernel version mismatch |
227 +--------------------------------------+--------------------------------------+
228 | JIRA: APEX-179 | DNS settings not working properly |
229 | | for baremetal deployments |
230 +--------------------------------------+--------------------------------------+
231 | JIRA: APEX-203 | Swift proxy enabled and fails in noha|
233 +--------------------------------------+--------------------------------------+
234 | JIRA: APEX-230 | Tacker heat_uri setting is wrong |
235 +--------------------------------------+--------------------------------------+
236 | JIRA: APEX-241 | Glance services are not running after|
238 +--------------------------------------+--------------------------------------+
239 | JIRA: APEX-265 | Metadata problems with os-odl_l2-sfc |
241 +--------------------------------------+--------------------------------------+
242 | JIRA: APEX-271 | L3 agent interface_driver set |
243 | | incorrectly for nosdn fdio noha |
244 +--------------------------------------+--------------------------------------+
245 | JIRA: APEX-275 | Metadata fails in ODL Boron |
246 +--------------------------------------+--------------------------------------+
247 | JIRA: APEX-278 | Duplicate neutron config class |
248 | | declaration for SDNVPN |
249 +--------------------------------------+--------------------------------------+
250 | JIRA: APEX-281 | ONOS sometimes fails to provide |
251 | | addresses to instances |
252 +--------------------------------------+--------------------------------------+
253 | JIRA: APEX-283 | Change networking-vpp ML2 driver to |
255 +--------------------------------------+--------------------------------------+
256 | JIRA: APEX-284 | vpp and hc versions for os-odl_l2 |
257 | | -fdio-noha scenario |
258 +--------------------------------------+--------------------------------------+
259 | JIRA: APEX-285 | Remove vlan-strip-offload off config |
260 | | from os-odl_l2-fdio-noha scenario |
261 +--------------------------------------+--------------------------------------+
262 | JIRA: APEX-286 | Make fdio repo an option in puppet- |
264 +--------------------------------------+--------------------------------------+
265 | JIRA: APEX-289 | Set undercloud VM to autostart for |
267 +--------------------------------------+--------------------------------------+
268 | JIRA: APEX-291 | link to apex installer missing on |
269 | | OPNFV download site |
270 +--------------------------------------+--------------------------------------+
271 | JIRA: APEX-293 | tenant_nic is assumed to be a virtual|
272 | | name for nosdn fdio scenario |
273 +--------------------------------------+--------------------------------------+
274 | JIRA: APEX-294 | dns server settings is ignored from |
275 | | network_settings.yaml |
276 +--------------------------------------+--------------------------------------+
277 | JIRA: APEX-297 | Add details in "11.2 Creating a Node |
278 | | Inventory File" |
279 +--------------------------------------+--------------------------------------+
280 | JIRA: APEX-326 | Consolidate SFC rpm into regular Apex|
282 +--------------------------------------+--------------------------------------+
283 | JIRA: APEX-331 | Conditionally install OVS NSH in |
284 | | ONOS Deployment |
285 +--------------------------------------+--------------------------------------+
286 | JIRA: APEX-332 | IPv6 Scenario fails to deploy |
287 +--------------------------------------+--------------------------------------+
288 | JIRA: APEX-333 | OVS DPDK does not work with UCS |
289 +--------------------------------------+--------------------------------------+
290 | JIRA: APEX-334 | ONOS SFC not using SFC version of OVS|
291 +--------------------------------------+--------------------------------------+
292 | JIRA: APEX-335 | Performance settings missing in |
293 | | os-odl_l2-fdio-ha.yaml |
294 +--------------------------------------+--------------------------------------+
295 | JIRA: APEX-163 | Prefix to mask calculation doesn't |
297 +--------------------------------------+--------------------------------------+
298 | JIRA: APEX-266 | ntp server shoudl be in network |
300 +--------------------------------------+--------------------------------------+
301 | JIRA: APEX-292 | unclear that ip ranges in network |
302 | | settings may not overlap |
303 +--------------------------------------+--------------------------------------+
304 | JIRA: APEX-349 | puppet-keystone failures in Colorado |
305 | | errors deplyoment |
306 +--------------------------------------+--------------------------------------+
307 | JIRA: APEX-344 | Update vpp/hc from 16.09 to 17.01 |
308 +--------------------------------------+--------------------------------------+
309 | JIRA: APEX-346 | Update ODL to Carbon for FDIO |
311 +--------------------------------------+--------------------------------------+
312 | JIRA: APEX-347 | Add deploy setting for ceph_device |
313 +--------------------------------------+--------------------------------------+
314 | JIRA: APEX-341 | FDIO scenarios: not supplying |
315 | | main-core and core-list workers |
316 | | causes deploy failure |
317 +--------------------------------------+--------------------------------------+
318 | JIRA: APEX-343 | Update qemu for fdio scenarios |
319 +--------------------------------------+--------------------------------------+
320 | JIRA: APEX-344 | nosdn fdio scenario missing iommu |
322 +--------------------------------------+--------------------------------------+
323 | JIRA: APEX-337 | enable isolcpu on kernel and pin vpp |
324 | | to the unused CPU for FDIO scenarios |
325 +--------------------------------------+--------------------------------------+
326 | JIRA: APEX-338 | Install Procedure for baremetal |
328 +--------------------------------------+--------------------------------------+
333 Software Deliverables
334 ~~~~~~~~~~~~~~~~~~~~~
336 - Apex release .rpm (opnfv-apex-release)
337 - Apex overcloud .rpm (opnfv-apex) - For nosdn and OpenDaylight Scenarios
338 - Apex overcloud onos .rpm (opnfv-apex-onos) - ONOS Scenarios
339 - Apex undercloud .rpm (opnfv-apex-undercloud)
340 - Apex common .rpm (opnfv-apex-common)
341 - build.sh - Builds the above artifacts
342 - opnfv-deploy - Automatically deploys Target OPNFV System
343 - opnfv-clean - Automatically resets a Target OPNFV Deployment
344 - opnfv-util - Utility to connect to or debug Overcloud nodes + OpenDaylight
346 Documentation Deliverables
347 ~~~~~~~~~~~~~~~~~~~~~~~~~~
348 - OPNFV Installation instructions for the Colorado release with the Apex
349 deployment toolchain - ver. 3.0
350 - OPNFV Release Notes for the Colorado release with the Apex deployment
351 toolchain - ver. 2.2.0 (this document)
353 Known Limitations, Issues and Workarounds
354 =========================================
359 **Max number of blades:** 1 Apex undercloud, 3 Controllers, 20 Compute blades
361 **Min number of blades:** 1 Apex undercloud, 1 Controller, 1 Compute blade
363 **Storage:** Ceph is the only supported storage configuration.
365 **Min master requirements:** At least 16GB of RAM for baremetal jumphost,
366 24GB for virtual deployments (noHA).
374 +--------------------------------------+--------------------------------------+
375 | **JIRA REFERENCE** | **SLOGAN** |
377 +--------------------------------------+--------------------------------------+
378 | JIRA: APEX-112 | ODL route local subnet traffic to GW |
379 +--------------------------------------+--------------------------------------+
380 | JIRA: APEX-149 | OpenFlow rules are populated slowly |
381 +--------------------------------------+--------------------------------------+
382 | JIRA: APEX-268 | VMs with multiple floating IPs can |
383 | | only access first NIC |
384 +--------------------------------------+--------------------------------------+
385 | JIRA: APEX-270 | Glance v2 api does not support url |
387 +--------------------------------------+--------------------------------------+
388 | JIRA: APEX-272 | Enable VLAN tenant networking and |
389 | | ability to configure range |
390 +--------------------------------------+--------------------------------------+
391 | JIRA: APEX-280 | Deleted network not cleaned up on |
393 +--------------------------------------+--------------------------------------+
394 | JIRA: APEX-290 | Instances cannot connect to metadata |
395 | | service after cluster reboot |
396 +--------------------------------------+--------------------------------------+
397 | JIRA: APEX-295 | VLAN tenant networking does not work |
398 | | in OVS DPDK scenario |
399 +--------------------------------------+--------------------------------------+
400 | JIRA: APEX-339 | OVS DPDK PMD is not CPU pinned |
401 +--------------------------------------+--------------------------------------+
402 | JIRA: APEX-355 | Undercloud CPU, RAM, Disk cannot be |
404 +--------------------------------------+--------------------------------------+
405 | JIRA: APEX-345 | Dashboard links time-out due to |
406 | | running out of file descriptors for |
408 +--------------------------------------+--------------------------------------+
409 | JIRA: APEX-215 | Keystone services not configured and |
410 | | the error is silently ignored (VLAN |
412 +--------------------------------------+--------------------------------------+
413 | JIRA: APEX-208 | Need ability to specify which NIC to |
415 +--------------------------------------+--------------------------------------+
416 | JIRA: APEX-254 | Add dynamic hugepages configuration |
417 +--------------------------------------+--------------------------------------+
418 | JIRA: APEX-138 | Unclear error message when interface |
420 +--------------------------------------+--------------------------------------+
427 Scenario specific release notes
428 ===============================
430 Scenario os-odl_l3-nofeature known issues
431 -----------------------------------------
433 * `APEX-112 <https://jira.opnfv.org/browse/APEX-112>`_:
434 ODL routes local subnet traffic to GW
436 Scenario os-odl_l2-nofeature known issues
437 -----------------------------------------
439 * `APEX-149 <https://jira.opnfv.org/browse/APEX-149>`_:
440 Openflow rules are populated very slowly
442 Scenario os-odl_l2-bgpvpn known issues
443 --------------------------------------
447 Scenario os-onos-nofeature known issues
448 ---------------------------------------
452 Scenario os-onos-sfc known issues
453 ---------------------------------
455 * `APEX-281 <https://jira.opnfv.org/browse/APEX-281>`_:
456 ONOS sometimes fails to provide addresses to instances
458 Scenario os-odl_l2-sfc-noha known issues
459 ----------------------------------------
463 Scenario os-nosdn-ovs known issues
464 ----------------------------------
468 Scenario os-odl_l2-fdio-noha known issues
469 -----------------------------------------
471 * `FDS-121 <https://jira.opnfv.org/browse/FDS-121>`_:
472 qemu doesn't receive connection on socket, vhost-user reconnect problem
473 * `FDS-62 <https://jira.opnfv.org/browse/FDS-62>`_:
474 APEX - Increase number of files MariaDB can open
475 * `FDS-79 <https://jira.opnfv.org/browse/FDS-79>`_:
476 Sometimes (especially in bulk crete/delete operations
477 when multiple networks/ports are created within short time)
478 OpenDaylight doesn't accept creation requests
479 * `FDS-81 <https://jira.opnfv.org/browse/FDS-81>`_:
480 After functest finishes there are two bds on computes and
482 * `APEX-217 <https://jira.opnfv.org/browse/APEX-217>`_:
483 qemu not configured with correct group:user
484 * `APEX-337 <https://jira.opnfv.org/browse/APEX-337>`_:
485 enable isolcpu on kernel and pin vpp to unused cpu for fdio scenarios
487 Scenario os-nosdn-fdio-noha known issues
488 ----------------------------------------
490 Note that a set of manual configration steps need to be performed
491 post an automated deployment for the scenario to be fully functional.
492 Please refer to `FDS-159 <https://jira.opnfv.org/browse/FDS-159>`_ and
493 `FDS-160 <https://jira.opnfv.org/browse/FDS-160>`_ for details.
495 * `FDS-155 <https://jira.opnfv.org/browse/FDS-155>`_:
496 os-nosdn-fdio-noha scenario: tempest_smoke_serial causes
497 mariadb/mysqld process to hang
498 * `FDS-156 <https://jira.opnfv.org/browse/FDS-156>`_:
499 os-nosdn-fdio-noha scenario: Race conditions for
500 network-vif-plugged notification
501 * `FDS-157 <https://jira.opnfv.org/browse/FDS-157>`_:
502 os-nosdn-fdio-noha scenario: Intermittently VMs
503 would get assigned 2 IPs instead of 1
504 * `FDS-158 <https://jira.opnfv.org/browse/FDS-158>`_:
505 os-nosdn-fdio-noha scenario: VM start/launch fails with
506 "no more IP addresses" in neutron logs
507 * `FDS-159 <https://jira.opnfv.org/browse/FDS-159>`_:
508 os-nosdn-fdio-noha scenario: Security groups not yet supported
509 * `FDS-160 <https://jira.opnfv.org/browse/FDS-160>`_:
510 os-nosdn-fdio-noha scenario: Vlan fix on controller
511 * `FDS-161 <https://jira.opnfv.org/browse/FDS-161>`_:
512 os-nosdn-fdio-noha scenario: VPP fails with certain UCS B-series blades
516 General HA scenario known issues
517 --------------------------------
519 * `COPPER-22 <https://jira.opnfv.org/browse/COPPER-22>`_:
520 Congress service HA deployment is not yet supported/verified.
521 * `APEX-276 <https://jira.opnfv.org/browse/APEX-276>`_:
522 ODL HA unstable and crashes frequently
527 The Colorado release with the Apex deployment toolchain has undergone QA
528 test runs with the OPNFV FuncTest project. The latest results per scenario
529 can be found `here <http://testresults.opnfv.org/reporting/functest/
530 release/colorado/index-status-apex.html>`_ for Colorado release.
536 For more information on the OPNFV Colorado release, please see:
538 http://wiki.opnfv.org/releases/Colorado
540 :Authors: Tim Rozet (trozet@redhat.com)
541 :Authors: Dan Radez (dradez@redhat.com)