summary |
shortlog |
log |
commit | commitdiff |
review |
tree
raw |
patch |
inline | side by side (from parent 1:
a1de279)
Corrected numbering of figiures in text and some minor editorial issues
Issue-ID: DOC-151
Change-Id: I60f89d3d11fbe6dd33f9b871a3c70aa8ba7f6de9
Signed-off-by: Pawel Pawlak <Pawel.Pawlak3@orange.com>
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright 2017 Huawei Technologies Co., Ltd.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright 2017 Huawei Technologies Co., Ltd.
services
- Carrier-grade scalability including horizontal scaling (linear
services
- Carrier-grade scalability including horizontal scaling (linear
- scale-out) and distribution to support large number of services
- and large networks
+ scale-out) and distribution to support large number of services
+ and large networks
- Metadata-driven and policy-driven architecture to ensure flexible
- Metadata-driven and policy-driven architecture to ensure flexible
- ways in which capabilities are used and delivered
+ ways in which capabilities are used and delivered
- The architecture shall enable sourcing best-in-class components
- The architecture shall enable sourcing best-in-class components
- Core capabilities shall support many diverse services
- The architecture shall support elastic scaling as needs grow or
- Core capabilities shall support many diverse services
- The architecture shall support elastic scaling as needs grow or
and policies (including recipes for corrective/remedial action) using
the ONAP Design Framework Portal.
and policies (including recipes for corrective/remedial action) using
the ONAP Design Framework Portal.
-|image1|\ **Figure 2:** ONAP Platform components (Amsterdam Release)
+|image1|\
+
+**Figure 2:** ONAP Platform components (Amsterdam Release)
The following sections describe the ONAP frameworks designed to address
these major requirements. The key pattern that these frameworks help
The following sections describe the ONAP frameworks designed to address
these major requirements. The key pattern that these frameworks help
-***Design -> Create -> Collect -> Analyze -> Detect -> Publish ->
-Respond.***
+**Design -> Create -> Collect -> Analyze -> Detect -> Publish ->
+Respond**
We refer to this automation pattern as “closed-loop automation” in that
it provides the necessary automation to proactively respond to network
and service conditions without human intervention. A high-level
schematic of the “closed-loop automation” and the various phases within
We refer to this automation pattern as “closed-loop automation” in that
it provides the necessary automation to proactively respond to network
and service conditions without human intervention. A high-level
schematic of the “closed-loop automation” and the various phases within
-the service lifecycle using the automation is depicted in Figure 4.
+the service lifecycle using the automation is depicted in Figure 3.
Closed-loop control is provided by Data Collection, Analytics and Events
(DCAE) and other ONAP components. Collectively, they provide FCAPS
Closed-loop control is provided by Data Collection, Analytics and Events
(DCAE) and other ONAP components. Collectively, they provide FCAPS
dependency on the underlying hardware.
In this use case, the customer has a physical CPE (pCPE) attached to a
dependency on the underlying hardware.
In this use case, the customer has a physical CPE (pCPE) attached to a
-traditional broadband network such as DSL (Figure 1). On top of this
+traditional broadband network such as DSL (Figure 4). On top of this
service, a tunnel is established to a data center hosting various VNFs.
In addition, depending on the capabilities of the pCPE, some functions
can be deployed on the customer site.
service, a tunnel is established to a data center hosting various VNFs.
In addition, depending on the capabilities of the pCPE, some functions
can be deployed on the customer site.
with legacy systems and physical function to establish VPN connectivity
in a brown field deployment.
with legacy systems and physical function to establish VPN connectivity
in a brown field deployment.
-The VoLTE use case, shown in Figure 6, demonstrates the use of the VF-C
+The VoLTE use case, shown in Figure 5, demonstrates the use of the VF-C
component and TOSCA-based data models to manage the virtualization
infrastructure.
component and TOSCA-based data models to manage the virtualization
infrastructure.