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
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
|
.. This document is protected/licensed under the following conditions
.. (c) Jonas Bjurel (Ericsson AB)
.. Licensed under a Creative Commons Attribution 4.0 International License.
.. You should have received a copy of the license along with this work.
.. If not, see <http://creativecommons.org/licenses/by/4.0/>.
========
Abstract
========
This document compiles the release notes for the Colorado 3.0 release of
OPNFV when using Fuel as a deployment tool, with an AArch64 (only) target
node pool.
===============
Important notes
===============
These notes provides release information for the use of Fuel as deployment
tool for the AArch64 Colorado 3.0 release of OPNFV.
The goal of the AArch64 Colorado release and this Fuel-based deployment process
is to establish a lab ready platform accelerating further development
of the OPNFV on AArch64 infrastructure.
Due to early docker and nodejs support on AArch64, we will still use an
x86_64 Fuel Master to build and deploy an AArch64 target pool.
Although not currently supported, mixing x86_64 and AArch64 architectures
inside the target pool will be possible later.
Carefully follow the installation-instructions provided in *Reference 13*.
=======
Summary
=======
For AArch64 Colorado, the typical use of Fuel as an OpenStack installer is
supplemented with OPNFV unique components such as:
- `OpenDaylight <http://www.opendaylight.org/software>`_ version "Boron" [1]_ - 'http://www.opendaylight.org/software'
- `Open vSwitch for NFV <https://wiki.opnfv.org/ovsnfv>`_ 'https://wiki.opnfv.org/ovsnfv'
- `BGPVPN <http://docs.openstack.org/developer/networking-bgpvpn>`_ 'http://docs.openstack.org/developer/networking-bgpvpn/'
- Tacker <https://wiki.openstack.org/wiki/Tacker>`_ 'https://wiki.openstack.org/wiki/Tacker'
The following OPNFV plugins are not yet ported for AArch64:
- `ONOS <http://onosproject.org/>`_ version "Drake" - 'http://onosproject.org/'
- `Service function chaining <https://wiki.opnfv.org/service_function_chaining>`_ 'https://wiki.opnfv.org/service_function_chaining'
- `SDN distributed routing and VPN <https://wiki.opnfv.org/sdnvpn>`_ 'https://wiki.opnfv.org/sdnvpn'
- `NFV Hypervisors-KVM <https://wiki.opnfv.org/nfv-kvm>`_ 'https://wiki.opnfv.org/nfv-kvm'
- `VSPERF <https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases>`_ 'https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases'
As well as OPNFV-unique configurations of the Hardware- and Software stack.
This Colorado artifact provides Fuel as the deployment stage tool in the
OPNFV CI pipeline including:
- Documentation built by Jenkins
- overall OPNFV documentation
- this document (release notes)
- installation instructions
- build-instructions
- The Colorado Fuel installer image AArch64 (.iso) built by Jenkins
- Automated deployment of Colorado with running on bare metal or a nested hypervisor environment (KVM)
- Automated validation of the Colorado deployment
============
Release Data
============
+--------------------------------------+--------------------------------------+
| **Project** | armband |
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | colorado.3.0 |
| | |
+--------------------------------------+--------------------------------------+
| **Release designation** | Colorado 3.0 follow-up release |
| | |
+--------------------------------------+--------------------------------------+
| **Release date** | December 05 2016 |
| | |
+--------------------------------------+--------------------------------------+
| **Purpose of the delivery** | Colorado alignment to Released |
| | Fuel 9.0 baseline + Bug-fixes for |
| | the following feaures/scenarios: |
| | - Open vSwitch for NFV |
| | - OpenDaylight |
| | - Tacker |
| | |
+--------------------------------------+--------------------------------------+
Version change
==============
Module version changes
----------------------
This is the Colorado 3.0 follow-up release.
It is based on following upstream versions:
- Fuel 9.0 Base release
- OpenStack Mitaka release
- OpenDaylight Boron release [1]_
Document changes
----------------
This is the Colorado 3.0 follow-up release.
It comes with the following documentation:
- Installation instructions - *Reference 13* - **Changed**
- Build instructions - *Reference 14* - **Changed**
- Release notes - *Reference 15* - **Changed** (This document)
Reason for version
==================
Feature additions
-----------------
**JIRA TICKETS:**
-
Bug corrections
---------------
**JIRA TICKETS:**
`Workarounds <https://jira.opnfv.org/issues/?filter=11404>`_ 'https://jira.opnfv.org/issues/?filter=11404'
(Also See respective Integrated feature project's bug tracking)
Deliverables
============
Software deliverables
---------------------
AArch64 Fuel-based installer iso file found in *Reference 2*
Documentation deliverables
--------------------------
- Installation instructions - *Reference 13*
- Build instructions - *Reference 14*
- Release notes - *Reference 15* (This document)
=========================================
Known Limitations, Issues and Workarounds
=========================================
System Limitations
==================
- **Max number of blades:** 1 Fuel master, 3 Controllers, 20 Compute blades
- **Min number of blades:** 1 Fuel master, 1 Controller, 1 Compute blade
- **Storage:** Ceph is the only supported storage configuration
- **Max number of networks:** 65k
- **Fuel master arch:** x86_64
- **Target node arch:** aarch64
Known issues
============
**JIRA TICKETS:**
`Known issues <https://jira.opnfv.org/issues/?filter=11405>`_ 'https://jira.opnfv.org/issues/?filter=11405'
(Also See respective Integrated feature project's bug tracking)
Workarounds
===========
**JIRA TICKETS:**
-
(Also See respective Integrated feature project's bug tracking)
============
Test results
============
The Colorado 3.0 release with the Fuel deployment tool has undergone QA test
runs, see separate test results.
==========
References
==========
For more information on the OPNFV Colorado 3.0 release, please see:
OPNFV
=====
1) `OPNFV Home Page <http://www.opnfv.org>`_ 'http://www.opnfv.org'
2) `OPNFV documentation- and software downloads <https://www.opnfv.org/software/download>`_ 'https://www.opnfv.org/software/download'
OpenStack
=========
3) `OpenStack Mitaka Release artifacts <http://www.openstack.org/software/mitaka>`_ 'http://www.openstack.org/software/mitaka'
4) `OpenStack documentation <http://docs.openstack.org>`_ 'http://docs.openstack.org'
OpenDaylight
============
5) `OpenDaylight artifacts <http://www.opendaylight.org/software/downloads>`_ 'http://www.opendaylight.org/software/downloads'
Fuel
====
6) `The Fuel OpenStack project <https://wiki.openstack.org/wiki/Fuel>`_: https://wiki.openstack.org/wiki/Fuel
7) `Fuel documentation overview <http://docs.openstack.org/developer/fuel-docs>`_: http://docs.openstack.org/developer/fuel-docs
8) `Fuel Installation Guide <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html>`_: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html
9) `Fuel User Guide <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html>`_: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html
10) `Fuel Developer Guide <http://docs.openstack.org/developer/fuel-docs/devdocs/develop.html>`_: http://docs.openstack.org/developer/fuel-docs/devdocs/develop.html
11) `Fuel Plugin Developers Guide <http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html>`_: http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html
12) `Fuel OpenStack Hardware Compatibility List <https://www.mirantis.com/products/openstack-drivers-and-plugins/hardware-compatibility-list>`_: https://www.mirantis.com/products/openstack-drivers-and-plugins/hardware-compatibility-list
Fuel in OPNFV
=============
13) `OPNFV Installation instruction for the AArch64 Colorado release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/armband/colorado/3.0/docs/installationprocedure/index.html>`_ 'http://artifacts.opnfv.org/armband/colorado/3.0/docs/installationprocedure/index.html'
14) `OPNFV Build instruction for the AArch64 Colorado release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/armband/colorado/3.0/docs/buildprocedure/index.html>`_ 'http://artifacts.opnfv.org/armband/colorado/3.0/docs/buildprocedure/index.html'
15) `OPNFV Release Note for the AArch64 Colorado release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/armband/colorado/3.0/docs/releasenotes/index.html>`_ 'http://artifacts.opnfv.org/armband/colorado/3.0/docs/releasenotes/index.html'
.. [1] OpenDaylight Boron RC2 is used when Service Function Chaining is enabled in Fuel plugin.
|
