1 .. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
3 .. Licensed under the Creative Commons License, Attribution 4.0 Intl.
4 (the "License"); you may not use this documentation except in compliance
5 with the License. You may obtain a copy of the License at
7 .. https://creativecommons.org/licenses/by/4.0/
9 .. Unless required by applicable law or agreed to in writing, software
10 distributed under the License is distributed on an "AS IS" BASIS,
11 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 See the License for the specific language governing permissions and
13 limitations under the License.
16 Requirement Changes Introduced in El Alto
17 ========================================================
19 This document summarizes the requirement changes by section that were
20 introduced between the Dublin release and
21 El Alto release. Click on the requirement number to
30 * **Requirements Added:** 1
31 * **Requirements Changed:** 14
32 * **Requirements Removed:** 2
35 Monitoring & Management > Data Structure Specification of the Event Record
36 --------------------------------------------------------------------------
47 The VNF or PNF provider **MUST** provide a YAML file formatted in adherence with
48 the :ref:`VES Event Registration specification <ves_event_registration_3_2>`
49 that defines the following information for each event produced by the VNF:
54 * Any special handling to be performed for that event
61 The events produced by the VNF or PNF **MUST** must be compliant with the common
62 event format defined in the
63 :ref:`VES Event Listener<ves_event_listener_7_1>`
71 The VNF or PNF provider **MUST** indicate specific conditions that may arise, and
72 recommend actions that may be taken at specific thresholds, or if specific
73 conditions repeat within a specified time interval, using the semantics and
74 syntax described by the :ref:`VES Event Registration specification <ves_event_registration_3_2>`.
77 ONAP Heat Orchestration Template Format > Heat Orchestration Template Structure > resources > properties
78 --------------------------------------------------------------------------------------------------------
89 A VNF's Heat Orchestration Template resource attribute ``property:``
90 **MUST NOT** use more than two levels of nested ``get_param`` intrinsic
91 functions when deriving a property value. SDC does not support nested
92 ``get_param`` with recursive lists (i.e., a list inside list).
93 The second ``get_param`` in a nested lookup must directly derive its value
94 without further calls to ``get_param`` functions.
96 * Example of valid nesting:
98 * ``name: {get_param: [ {vm-type}_names, {get_param : index } ] }``
100 * Examples of invalid nesting. SDC will not support these examples since
101 there is an array inside array.
103 * ``name: {get_param: [ {vm-type}_names, { get_param: [ indexlist, 0 ] } ] }``
104 * ``name: {get_param: [ {vm-type}_names, { get_param: [ indexlist1, { get_param: indexlist2 } ] } ] }``
107 ONAP Heat Orchestration Templates Overview > ONAP Heat Orchestration Template Filenames > Base Modules
108 ------------------------------------------------------------------------------------------------------
119 A VNF Heat Orchestration Template's Base Module file name **MUST** include
120 case insensitive 'base' in the filename and
121 **MUST** match one of the following four
124 1.) ``base_<text>.y[a]ml``
126 2.) ``<text>_base.y[a]ml``
130 4.) ``<text>_base_<text>``.y[a]ml
132 where ``<text>`` **MUST** contain only alphanumeric characters and
133 underscores '_' and **MUST NOT** contain the case insensitive string
134 ``base`` or ``volume``.
137 ONAP Heat Orchestration Templates Overview > ONAP Heat Orchestration Template Filenames > Cinder Volume Modules
138 ---------------------------------------------------------------------------------------------------------------
149 A VNF Heat Orchestration Template's Cinder Volume Module ``resources:``
151 **MUST** only be defined using one of the following:
153 * one of more ``OS::Cinder::Volume`` resources
154 * one or more ``OS::Heat::ResourceGroup`` resources that call a nested YAML
155 file that contains only ``OS::Cinder::Volume`` resources
156 * a resource that calls a nested YAML file (static nesting) that contains
157 only ``OS::Cinder::Volume`` resources
160 ONAP Heat Orchestration Templates Overview > ONAP Heat Orchestration Template Filenames > Incremental Modules
161 -------------------------------------------------------------------------------------------------------------
172 VNF Heat Orchestration Template's Incremental Module file name
173 **MUST** contain only alphanumeric characters and underscores
174 '_' and **MUST NOT** contain the case insensitive string ``base``.
177 ONAP Heat Orchestration Templates Overview > ONAP Heat Orchestration Template Filenames > Nested Heat file
178 ----------------------------------------------------------------------------------------------------------
189 VNF Heat Orchestration Template's Nested YAML file name **MUST** contain
190 only alphanumeric characters and underscores '_' and
191 **MUST NOT** contain the case insensitive string ``base``.
194 Resource: OS::Nova::Server - Parameters
195 ---------------------------------------
206 A VNF's Heat Orchestration Template's ``OS::Nova::Server`` resource's
208 * Resource ID (defined in R-29751)
209 * property ``image`` parameter name (defined in R-58670)
210 * property ``flavor`` parameter name (defined in R-45188)
211 * property ``name`` parameter name (defined in R-54171 & R-87817)
212 * property ``networks`` map property ``port`` value which is a
213 ``OS::Neutron::Port`` Resource ID (defined in R-20453)
214 referenced using the intrinsic function ``get_attr``
216 **MUST** contain the identical ``{vm-type}``
217 and **MUST** follow the naming conventions defined
218 in R-58670, R-45188, R-54171, R-87817, and R-29751. And the ``{index}`` in
219 the ``OS::Nova::Server`` Resource ID (defined in R-29751) **MUST** match
220 the ``{vm-type_index}`` defined in
221 the ``OS::Nova::Server`` property ``networks`` map property ``port``
222 referenced ``OS::Neutron::Port`` Resource ID (defined in R-20453).
225 Resource: OS::Nova::Server - Parameters > Property: availability_zone
226 ---------------------------------------------------------------------
237 A VNF's Heat Orchestration Template's Resource ``OS::Nova::Server``
238 property ``availability_zone`` parameter name **MAY** change when
239 past into a nested YAML file.
250 A VNF's Heat Orchestration Template's base module or incremental module
251 resource ``OS::Nova::Server``
252 property ``availability_zone`` parameter
253 **MUST** follow the naming convention
255 * ``availability_zone_{index}``
257 where ``{index}`` is a numeric value that **MUST** start at zero
258 in a VNF's Heat Orchestration Templates and **MUST**
266 The VNF's Heat Orchestration Template's base module or incremental module
267 resource ``OS::Nova::Server`` property
268 ``availability_zone`` parameter **MUST** be declared as type: ``string``.
271 VNF On-boarding and package management > Resource Control Loop
272 --------------------------------------------------------------
283 The VNF or PNF Package **MUST** include documentation which must include
284 all events (fault, measurement for VNF or PNF Scaling, Syslogs, State Change
285 and Mobile Flow), that need to be collected at each VM, VNFC (defined in `VNF Guidelines <https://onap.readthedocs.io/en/latest/submodules/vnfrqts/guidelines.git/docs/vnf_guidelines.html>`__ ) and for the overall VNF or PNF.
288 VNF On-boarding and package management > Resource Description
289 -------------------------------------------------------------
300 The VNF or PNF package **MUST** provide :ref:`VES Event Registration <ves_event_registration_3_2>`
301 for all VES events provided by that VNF or PNF.
304 VNF Security > VNF General Security Requirements
305 ------------------------------------------------
316 VNFs that are subject to regulatory requirements **MUST** provide
317 functionality that enables the Operator to comply with ETSI TC LI
318 requirements, and, optionally, other relevant national equivalents.
321 VNF Security > VNF Identity and Access Management Requirements
322 --------------------------------------------------------------
333 The VNF **MUST**, if not integrated with the Operator's Identity and
334 Access Management system, support Role-Based Access Control to enforce
338 VNF Security > VNF Security Analytics Requirements
339 --------------------------------------------------
350 The VNF **MUST** support Integration functionality via
351 API/Syslog/SNMP to other functional modules in the network (e.g.,
352 PCRF, PCEF) that enable dynamic security control by blocking the
353 malicious traffic or malicious end users.