diff --git a/404.html b/404.html
index 812b476f..5de666d6 100644
--- a/404.html
+++ b/404.html
@@ -1,3 +1,8 @@
+
+
---
layout: openness
---
diff --git a/README.md b/README.md
index 09e2057a..7fb04814 100644
--- a/README.md
+++ b/README.md
@@ -18,6 +18,7 @@ Below is the complete list of OpenNESS solution documentation
## Architecture
* [architecture.md: OpenNESS Architecture overview](https://github.com/open-ness/specs/blob/master/doc/architecture.md)
+* [flavors.md: OpenNESS Deployment Flavors](https://github.com/open-ness/specs/blob/master/doc/flavors.md)
## Getting Started - Setup
@@ -39,6 +40,7 @@ Below is the complete list of OpenNESS solution documentation
* [openness-edgedns.md: Using edge DNS service](https://github.com/open-ness/specs/blob/master/doc/applications-onboard/openness-edgedns.md)
* [openness-interface-service.md: Using network interfaces management service](https://github.com/open-ness/specs/blob/master/doc/applications-onboard/openness-interface-service.md)
* [using-openness-cnca.md: Steps for configuring 4G CUPS or 5G Application Function for Edge deployment for Network and OnPremises Edge](https://github.com/open-ness/specs/blob/master/doc/applications-onboard/using-openness-cnca.md)
+ * [openness-eaa.md: Edge Application Agent: Description of Edge Application APIs and Edge Application Authentication APIs](https://github.com/open-ness/specs/blob/master/doc/applications-onboard/openness-eaa.md)
## Radio Access Network (RAN)
* [ran: Folder containing details of 4G and 5G RAN deployment support](https://github.com/open-ness/specs/tree/master/doc/ran)
@@ -67,6 +69,7 @@ Below is the complete list of OpenNESS solution documentation
* [openness-tunable-exec.md: Configurable startup command support for containers in OpenNESS](https://github.com/open-ness/specs/blob/master/doc/enhanced-platform-awareness/openness-tunable-exec.md)
* [openness-port-forward.md: Support for setting up port forwarding of a container in OpenNESS On-Prem mode](https://github.com/open-ness/specs/blob/master/doc/enhanced-platform-awareness/openness-port-forward.md)
* [openness-shared-storage.md: Shared storage for containers in OpenNESS On-Prem mode](https://github.com/open-ness/specs/blob/master/doc/enhanced-platform-awareness/openness-shared-storage.md)
+ * [openness-vca.md: Visual Compute Accelerator Card - Analytics (VCAC-A)](https://github.com/open-ness/specs/blob/master/doc/enhanced-platform-awareness/openness-vcac-a.md)
## Dataplane
@@ -99,6 +102,9 @@ Below is the complete list of OpenNESS solution documentation
* [Edge Virtualization Infrastructure API: EVA](https://github.com/open-ness/specs/blob/master/schema/pb/eva.proto)
* [schema: Folder containing APIs protobuf or schema for varios endpoints in OpenNESS solution](https://github.com/open-ness/specs/tree/master/schema)
+## Orchestration
+* [openness-helm.md: Helm support in OpenNESS](https://github.com/open-ness/specs/blob/master/doc/orchestration/openness-helm.md)
+
## Release history
* [openness_releasenotes.md: This document provides high level system features, issues and limitations information for OpenNESS](https://github.com/open-ness/specs/blob/master/openness_releasenotes.md)
@@ -108,3 +114,51 @@ Below is the complete list of OpenNESS solution documentation
* [OpenNESS Website - Developers : Website containing developer resources](https://www.openness.org/developers)
* [Intel Network Builders OpenNESS training ](https://builders.intel.com/university/networkbuilders/coursescategory/open-network-edge-services-software-openness)
+## List of Abbreviations
+- 3GPP: Third Generation Partnership Project
+- CUPS: Control and User Plane Separation of EPC Nodes
+- AF: Application Function
+- API: Application Programming Interface
+- APN: Access Point Name
+- EPC: Evolved Packet Core
+- ETSI: European Telecommunications Standards Institute
+- FQDN: Fully Qualified Domain Name
+- HTTP: Hyper Text Transfer Protocol
+- IMSI: International Mobile Subscriber Identity
+- JSON: JavaScript Object Notation
+- MEC: Multi-Access Edge Computing
+- OpenNESS: Open Network Edge Services Software
+- LTE: Long-Term Evolution
+- MCC: Mobile Country Code
+- MME: Mobility Management Entity
+- MNC: Mobile Network Code
+- NEF: Network Exposure Function
+- OAM: Operations, Administration and Maintenance
+- PDN: Packet Data Network
+- PFCP: Packet Forwarding Control Protocol- SGW: Serving Gateway- PGW: PDN Gateway
+- PGW-C: PDN Gateway - Control Plane Function
+- PGW-U: PDN Gateway - User Plane Function
+- REST: REpresentational State Transfer
+- SGW-C: Serving Gateway - Control Plane Function
+- SGW-U: Serving Gateway - User Plane Function
+- TAC: Tracking Area Code
+- UE: User Equipment (in the context of LTE)
+- VIM: Virtual Infrastructure Manager
+- UUID: Universally Unique IDentifier
+- AMF: Access and Mobility Mgmt Function
+- SMF: Session Management Function
+- AUSF: Authentication Server Function
+- NEF: Network Exposure Function
+- NRF: Network function Repository Function
+- UDM: Unified Data Management
+- PCF: Policy Control Function
+- UPF: User Plane Function
+- DN: Data Network
+- AF: Application Function
+- SR-IOV: Single Root I/O Virtualization
+- NUMA: Non-Uniform Memory Access
+- COTS: Commercial Off-The-Shelf
+- DU: Distributed Unit of RAN
+- CU: Centralized Unit of RAN
+- OEK: OpenNESS Experience Kit
+- IDO: Intel Distribution of OpenNESS
\ No newline at end of file
diff --git a/_data/navbars/applications-onboarding.yml b/_data/navbars/applications-onboarding.yml
index ab50ea08..8a720d2c 100644
--- a/_data/navbars/applications-onboarding.yml
+++ b/_data/navbars/applications-onboarding.yml
@@ -1,3 +1,6 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Application Onboarding"
path: /applications-onboard/
order: 2
@@ -6,23 +9,33 @@ section:
path: /doc/applications-onboard/network-edge-applications-onboarding
meta_title: OpenNESS Network Edge Application On-Boarding Process
meta_description: OpenNESS application on-boarding process for the Network Edge provides instructions on how to deploy an application from the Edge Controller to Edge Nodes in the cluster.
-
+
- title: OnPremises Applications Onboarding
path: /doc/applications-onboard/on-premises-applications-onboarding
meta_title: OpenNESS OnPremises Mode Application On-Boarding Process
meta_description: OpenNESS application on-boarding process for the OnPremises mode provides instructions on how to deploy an application from the Edge Controller on Edge Nodes.
-
- - title: OpenNESS Edge DNS
+
+ - title: Edge DNS
path: /doc/applications-onboard/openness-edgedns
meta_title: OpenNESS Provides Edge DNS and Supports DNS Microservice
meta_description: OpenNESS edge platform is required to provides access to DNS. The edge platform receives the application DNS rules from the controller.
-
- - title: OpenNESS Interface Service
+
+ - title: Edge Application Agent (EAA)
+ path: /doc/applications-onboard/openness-eaa
+ meta_title: Edge Application Agent (EAA)
+ meta_description: OpenNESS enables Edge Applications to produce, discover and consume services that are available on the OpenNESS cluster through the Edge Application Agent (EAA) APIs.
+
+ - title: Interface Service
path: /doc/applications-onboard/openness-interface-service
meta_title: OpenNESS Applications Onboard - OpenNESS Interface Service
meta_description: OpenNESS Interface service is an application running in Kubernetes pod on every worker node of OpenNESS Kubernetes cluster and provides OVS bridge, enabling external traffic scenarios.
-
- - title: Using OpenNESS CNCA
+
+ - title: VM support in OpenNESS for Network Edge
+ path: /doc/applications-onboard/openness-network-edge-vm-support
+ meta_title: VM support in OpenNESS for Network Edge
+ meta_description: VM support in OpenNESS for Network Edge - Setup, deployment, and management considerations.
+
+ - title: Core Network Configuration Agent (CNCA)
path: /doc/applications-onboard/using-openness-cnca
meta_title: OpenNESS 4G/LTE Core Configuration Using CNCA
- meta_description: CNCA provides a kubectl plugin to configure the 4G/LTE Core network. Kubernetes adopts plugins concepts to extend its functionality executes CNCA related functions.
\ No newline at end of file
+ meta_description: CNCA provides a kubectl plugin to configure the 4G/LTE Core network. Kubernetes adopts plugins concepts to extend its functionality executes CNCA related functions.
diff --git a/_data/navbars/cloud-adapters.yml b/_data/navbars/cloud-adapters.yml
index 6dc7a20f..12b7f045 100644
--- a/_data/navbars/cloud-adapters.yml
+++ b/_data/navbars/cloud-adapters.yml
@@ -1,13 +1,16 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Cloud Adapters"
path: /cloud-adapters/
order: 8
section:
- - title: OpenNESS AWS Greengrass
+ - title: AWS Greengrass
path: /doc/cloud-adapters/openness_awsgreengrass
meta_title: OpenNESS Integration with AWS Greengrass
meta_description: OpenNESS is an open source software platform that enables easy orchestration of edge services across diverse network platform and access technologies in multi-cloud environments.
- - title: OpenNESS Baidu Cloud
+ - title: Baidu Cloud
path: /doc/cloud-adapters/openness_baiducloud
meta_title: OpenNESS Integration with Baidu OpenEdge
- meta_description: OpenNESS can integrate with Baidu Cloud Connector, OpenEdge which is Edge IoT Gateway. Baidu Edge solution is called as Baidu® IntelliEdge.
\ No newline at end of file
+ meta_description: OpenNESS can integrate with Baidu Cloud Connector, OpenEdge which is Edge IoT Gateway. Baidu Edge solution is called as Baidu® IntelliEdge.
diff --git a/_data/navbars/core-network-4G-5G.yml b/_data/navbars/core-network-4G-5G.yml
index 49ced49c..4e119d09 100644
--- a/_data/navbars/core-network-4G-5G.yml
+++ b/_data/navbars/core-network-4G-5G.yml
@@ -1,18 +1,21 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Core Network - 4G and 5G"
path: /core-network/
order: 4
section:
- - title: OpenNESS EPC
+ - title: Evolved Packet Core (EPC)
path: /doc/core-network/openness_epc
- meta_title: OpenNESS Edge Cloud Deployment with 3GPP 4G LTE CUPS of EPC
+ meta_title: Edge Cloud Deployment with 3GPP 4G LTE CUPS of EPC
meta_description: OpenNESS is an open source edge computing platform that enables Service Providers and Enterprises to deploy applications and services on a network edge.
- - title: OpenNESS NGC
+ - title: Next-Gen Core (NGC)
path: /doc/core-network/openness_ngc
- meta_title: OpenNESS Edge Cloud Deployment with 3GPP 5G Stand Alone
+ meta_title: Edge Cloud Deployment with 3GPP 5G Stand Alone
meta_description: OpenNESS NGC provides reference REST-based APIs along with 3GPP standard traffic influencing APIs to address some of these major challenges in 5G edge deployments.
- - title: OpenNESS UPF
+ - title: User Plane Function (UPF)
path: /doc/core-network/openness_upf
- meta_title: OpenNESS User Plane Function UPF
- meta_description: User Plane Function is the evolution of Control and User Plane Separation which part of the Rel.14 in Evolved Packet core. CUPS enabled PGW to be split into PGW-C and PGW-U.
\ No newline at end of file
+ meta_title: User Plane Function (UPF)
+ meta_description: User Plane Function is the evolution of Control and User Plane Separation which part of the Rel.14 in Evolved Packet core. CUPS enabled PGW to be split into PGW-C and PGW-U.
diff --git a/_data/navbars/dataplane.yml b/_data/navbars/dataplane.yml
index bb992d87..f7b18525 100644
--- a/_data/navbars/dataplane.yml
+++ b/_data/navbars/dataplane.yml
@@ -1,23 +1,26 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Dataplane"
path: /dataplane/
order: 6
section:
- - title: OpenNESS InterAPP
+ - title: Inter-App Communication
path: /doc/dataplane/openness-interapp
- meta_title: InterApp Communication Support in OpenNESS
- meta_description: OpenNESS provides InterApp Communication support for both the On-Premises and Network edge modes of OpenNESS.
+ meta_title: Inter-App Communication Support in OpenNESS
+ meta_description: OpenNESS provides Inter-App Communication support for both the On-Premises and Network edge modes of OpenNESS.
- - title: OpenNESS OVN
+ - title: OVN/OVS
path: /doc/dataplane/openness-ovn
meta_title: OpenNESS Support for OVS as Dataplane with OVN
meta_description: The primary objective of supporting OVN/OVS in OpenNESS is to demonstrate the capability of using a standard dataplane like OVS for an Edge Compute platform.
- - title: OpenNESS NTS
+ - title: NTS
path: /doc/dataplane/openness-nts
meta_title: OpenNESS NTS - Dataplane support for Edge Cloud between ENB and EPC Deployment
meta_description: OpenNESS NTS is a Dataplane component that provides a network traffic control service and a data forwarding service to mobile edge applications, specifically for S1-U deployments.
- - title: OpenNESS Userspace CNI
+ - title: Userspace CNI
path: /doc/dataplane/openness-userspace-cni
meta_title: OpenNESS Userspace CNI, Setup Userspace CNI
- meta_description: Userspace CNI is a Container Network Interface Kubernetes plugin that was designed to simplify the process of deployment of DPDK based applications in Kubernetes pods.
\ No newline at end of file
+ meta_description: Userspace CNI is a Container Network Interface Kubernetes plugin that was designed to simplify the process of deployment of DPDK based applications in Kubernetes pods.
diff --git a/_data/navbars/edge-applications.yml b/_data/navbars/edge-applications.yml
index f8904025..1e5d8ad4 100644
--- a/_data/navbars/edge-applications.yml
+++ b/_data/navbars/edge-applications.yml
@@ -1,19 +1,31 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Edge Applications"
path: /applications/
order: 7
section:
- - title: OpenNESS Application Guide
+ - title: Application Development & Porting Guide
path: /doc/applications/openness_appguide
- meta_title: Openness Application Development and Porting Guide
+ meta_title: Application Development and Porting Guide
meta_description: OpenNESS is an open source software toolkit to enable easy orchestration of edge services across diverse network platform and access technologies in multi-cloud environments.
-
- - title: OpenNESS OVC
+
+ - title: OVC Smart City Application
path: /doc/applications/openness_ovc
meta_title: Open Visual Cloud Smart City Application on OpenNESS
meta_description: The Open Visual Cloud is an open source project that offers a set of pre-defined reference pipelines for various target visual cloud use cases.
-
- - title: OpenNESS OpenVINO
+
+ - title: Intel OpenVINO Sample Application
path: /doc/applications/openness_openvino
meta_title: OpenVINO Sample Application in OpenNESS
- meta_description: OpenVINO toolkit, short for Open Visual Inference and Neural network Optimization toolkit, provides improved neural network performance on Intel processors.
-
\ No newline at end of file
+ meta_description: OpenVINO toolkit, short for Open Visual Inference and Neural network Optimization toolkit, provides improved neural network performance on Intel processors.
+
+ - title: OpenNESS Video Analytics Services
+ path: /doc/applications/openness_va_services
+ meta_title: OpenNESS Video Analytics Services
+ meta_description: The Video Analytics Services provided by OpenNESS to enable third party edge application to deploy and use hardware optimized video analytics pipelines.
+
+ - title: Industrial Edge Insights Application on OpenNESS
+ path: /doc/applications/openness_eis
+ meta_title: Industrial Edge Insights Application on OpenNESS — Solution Overview
+ meta_description: Intel Edge Insights Software (EIS) that brings ease of AI deployment in industrial environment through a set of integrated key capabilities.
diff --git a/_data/navbars/enhanced-platform-awareness.yml b/_data/navbars/enhanced-platform-awareness.yml
index 3766be9f..3591cb66 100644
--- a/_data/navbars/enhanced-platform-awareness.yml
+++ b/_data/navbars/enhanced-platform-awareness.yml
@@ -1,63 +1,76 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Enhanced Platform Awareness"
path: /enhanced-platform-awareness/
order: 5
section:
- - title: OpenNESS Hugepage
+ - title: Hugepage Support
path: /doc/enhanced-platform-awareness/openness-hugepage
meta_title: OpenNESS Enhanced Platform Awareness - Hugepage Support on OpenNESS
meta_description: Huge page support openness, added to Kubernetes v1.8, enables the discovery, scheduling, and allocation of huge pages as a native first-class resource.
-
- - title: OpenNESS Node Feature Discovery
+
+ - title: Node Feature Discovery Support
path: /doc/enhanced-platform-awareness/openness-node-feature-discovery
meta_title: Enhanced Platform Awareness - Node Feature Discovery Support in OpenNESS
meta_description: OpenNESS Node Feature Discovery is one of the Intel technologies that supports targeting of intelligent configuration and capacity consumption of platform capabilities.
-
- - title: OpenNESS SRIOV Multiple Interfaces
+
+ - title: Multiple Interface And PCIe SRIOV Support
path: /doc/enhanced-platform-awareness/openness-sriov-multiple-interfaces
meta_title: Enhanced Platform Awareness - Multiple Interface And PCIe SRIOV Support in OpenNESS
meta_description: Multiple Interface and PCIe SRIOV support in OpenNESS, OpenNESS Network Edge uses the Multus container network interface is a container network interface plugin for Kubernetes.
-
- - title: OpenNESS Dedicated Core
+
+ - title: Dedicated CPU Core
path: /doc/enhanced-platform-awareness/openness-dedicated-core
- meta_title: Dedicated CPU Core for Workload Support in OpenNESS - Enhanced Platform Awareness
+ meta_title: Enhanced Platform Awareness - Dedicated CPU Core for Workload Support in OpenNESS
meta_description: Multi-core COTS platforms are typical in any cloud or Cloudnative deployment. Parallel processing on multiple cores helps achieve better density.
-
- - title: OpenNESS BIOS
+
+ - title: BIOS and Firmware Configuration
path: /doc/enhanced-platform-awareness/openness-bios
meta_title: BIOS and Firmware Configuration on OpenNESS Platform
meta_description: BIOS and Firmware are the fundamental platform configurations of a typical Commercial off-the-shelf (COTS) platform.
-
- - title: OpenNESS FPGA
+
+ - title: FPGA Support
path: /doc/enhanced-platform-awareness/openness-fpga
- meta_title: FPGA in OpenNESS- Programming, Resource Allocation and Configuration
+ meta_title: FPGA in OpenNESS - Programming, Resource Allocation and Configuration
meta_description: The FPGA Programmable acceleration card plays a key role in accelerating certain types of workloads which in-turn increases the overall compute capacity of a COTS platform.
-
- - title: OpenNESS HDDL
+
+ - title: Intel® Movidius™ Myriad™ X HDDL Support
path: /doc/enhanced-platform-awareness/openness_hddl
meta_title: Intel® Movidius™ Myriad™ X HDDL Solution in OpenNESS
meta_description: Intel® Movidius™ Myriad™ X HDDL solution integrates multiple Myriad™ X SoCs in a PCIe add-in card form factor or a module form factor to build a scalable, high capacity deep learning solution.
-
- - title: OpenNESS Topology Manager
+
+ - title: Visual Compute Accelerator Card - Analytics (VCAC-A)
+ path: /doc/enhanced-platform-awareness/openness-vcac-a
+ meta_title: Visual Compute Accelerator Card - Analytics (VCAC-A)
+ meta_description: The Visual Cloud Accelerator Card - Analytics (VCAC-A) equips Intel® Xeon® Scalable Processor based platforms and Intel Movidius™ VPU to enhance the video codec, computer vision, and inference capabilities.
+
+ - title: Topology Manager Support
path: /doc/enhanced-platform-awareness/openness-topology-manager
meta_title: Topology Manager Support in OpenNESS, Resource Locality Awareness
meta_description: Topology Manager is a solution permitting k8s components like CPU Manager and Device Manager, to coordinate the resources allocated to a workload.
-
- - title: OpenNESS Environment Variables
+
+ - title: Environment Variables Support
path: /doc/enhanced-platform-awareness/openness-environment-variables
meta_title: Environment Variable Support in OpenNESS
meta_description: Environment variables can be configured when creating a new Docker container. Once the container is running, any application located in that container can detect and use the variable.
-
- - title: OpenNESS Tunable EXEC
+
+ - title: Tunable Execution
path: /doc/enhanced-platform-awareness/openness-tunable-exec
- meta_title: OpenNESS Tunable Exec - Overriding the Startup Command for Container
+ meta_title: Tunable Execution - Overriding the Startup Command for Container
meta_description: This feature enables you to override the start-up command for a container, thus removing the need to rebuild it just to make this change.
-
- - title: OpenNESS Port Forward
+
+ - title: Port Forwarding
path: /doc/enhanced-platform-awareness/openness-port-forward
- meta_title: OpenNESS Port Forward - Setting Up Port Forwarding of Container
+ meta_title: Setting Up Port Forwarding for Containers
meta_description: This feature enables the user to set up external network ports for their application (container) so that applications running on other hosts can connect.
-
- - title: OpenNESS Shared Storage
+
+ - title: Shared Storage for containers
path: /doc/enhanced-platform-awareness/openness-shared-storage
- meta_title: Shared Storage for Containers in Openness On-Prem Mode
+ meta_title: Shared Storage for Containers in Openness On-Premises Mode
meta_description: OpenNESS On-Prem mode provides possibility to use volume and bind mount storage models known from docker.
+
+ - title: Telemetry support in OpenNESS
+ path: /doc/enhanced-platform-awareness/openness-telemetry
+ meta_title: Telemetry support in OpenNESS
+ meta_description: OpenNESS supports platform and application telemetry allowing users to retrieve information about the platform, the underlying hardware, cluster and applications deployed.
diff --git a/_data/navbars/getting-started.yml b/_data/navbars/getting-started.yml
index 4e961fd6..2e3db138 100644
--- a/_data/navbars/getting-started.yml
+++ b/_data/navbars/getting-started.yml
@@ -1,3 +1,6 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Getting Started"
path: /getting-started/
order: 1
@@ -5,36 +8,35 @@ section:
- title: OpenNESS Experience Kits
path: /doc/getting-started/openness-experience-kits
meta_title: OpenNESS Experience Kits Easy Setup of OpenNESS in Network Edge
- meta_description: OpenNESS Experience Kits repository contains easy setup of OpenNESS in Network Edge, On-Premises modes, and playbooks deployment of the offline package.
-
+ meta_description: OpenNESS Experience Kits repository contains easy setup of OpenNESS in Network Edge and On-Premises modes.
+
- title: Network Edge
path:
section:
- - title: Controller Edge Node Setup
+ - title: Controller & Edge Node Setup
path: /doc/getting-started/network-edge/controller-edge-node-setup
- meta_title: OpenNESS Network Edge - Controller and Edge Node Setup
+ meta_title: Controller and Edge Node Setup
meta_description: OpenNESS Network Edge Controller and Edge nodes must be set up on different machines and provided in the inventory may reboot during the installation.
-
- - title: Supported EPA
+
+ - title: Enhanced Platform Awareness Features Supported
path: /doc/getting-started/network-edge/supported-epa
meta_title: OpenNESS Network Edge - Enhanced Platform Awareness Features Supported
meta_description: Enhanced Platform Awareness features supported for network edge is to expose capability to edge cloud orchestrator for better performance, consistency, and reliability.
-
+
- title: OnPremises
path:
section:
- - title: Controller Edge Node Setup
+ - title: Controller & Edge Node Setup
path: /doc/getting-started/on-premises/controller-edge-node-setup
- meta_title: OpenNESS OnPremises - Controller and Edge Node Setup
+ meta_title: Controller and Edge Node Setup
meta_description: OpenNESS Controller and Edge Node to work together the Edge Node needs to enroll with the Controller until it is serial key recognized by the Controller.
-
- - title: OpenNESS Gateway
+
+ - title: Gateway Feature
path: /doc/getting-started/on-premises/openness-gateway
- meta_title: OpenNESS Gateway Feature - Supported Mode of Operation
+ meta_title: Gateway Feature - Supported Mode of Operation
meta_description: OpenNESS gateway features to the supported mode of operation in this case still, the only requirement being the controller is on a publicly accessible network.
-
- - title: Supported EPA
+
+ - title: Enhanced Platform Awareness Features Supported
path: /doc/getting-started/on-premises/supported-epa
- meta_title: OpenNESS OnPremises - Enhanced Platform Awareness Features Supported
+ meta_title: Enhanced Platform Awareness Features Supported
meta_description: Enhanced Platform Awareness features are supported in OpenNESS OnPremises Edge using EVA APIs. OpenNESS controller UI user would use create the HTTP REST POST API.
-
\ No newline at end of file
diff --git a/_data/navbars/introduction.yml b/_data/navbars/introduction.yml
index eec2af18..38cbf161 100644
--- a/_data/navbars/introduction.yml
+++ b/_data/navbars/introduction.yml
@@ -1,9 +1,21 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Introduction"
path: /architecture/
order: 0
section:
-- title: Architecture
- path: /doc/architecture
- meta_title: OpenNESS Architecture And Solution Overview
- meta_description: OpenNESS is an open source software to enable easy orchestration of edge services and network functions across diverse network platform in multi-cloud environments.
-
\ No newline at end of file
+ - title: OpenNESS Architecture & Solution Overview
+ path: /doc/architecture
+ meta_title: OpenNESS Architecture And Solution Overview
+ meta_description: OpenNESS is an open source software to enable easy orchestration of edge services and network functions across diverse network platform in multi-cloud environments.
+
+ - title: OpenNESS Deployment Flavors
+ path: /doc/flavors
+ meta_title: OpenNESS Deployment Flavors
+ meta_description: Pre-defined deployment flavors using OpenNESS that are available in the OpenNESS Experience Kits.
+
+ - title: OpenNESS Helm
+ path: /doc/orchestration/openness-helm
+ meta_title: OpenNESS Helm
+ meta_description: OpenNESS supports Helm for user to package, configure, and deploy applications and services onto Kubernetes clusters.
diff --git a/_data/navbars/radio-access-network.yml b/_data/navbars/radio-access-network.yml
index 46ef8448..f5db3a36 100644
--- a/_data/navbars/radio-access-network.yml
+++ b/_data/navbars/radio-access-network.yml
@@ -1,8 +1,11 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Radio Access Network (RAN)"
path: /ran/
order: 3
section:
- - title: OpenNESS RAN
+ - title: OpenNESS Radio Access Network
path: /doc/ran/openness_ran
meta_title: OpenNESS Radio Access Network is the Edge of Wireless Network
- meta_description: OpenNESS Radio Access Network is the edge of the wireless network. OpenNESS Intel FlexRAN uses as a reference 4G and 5G base station for 4G and 5G end-to-end testing.
\ No newline at end of file
+ meta_description: OpenNESS Radio Access Network is the edge of the wireless network. OpenNESS Intel FlexRAN uses as a reference 4G and 5G base station for 4G and 5G end-to-end testing.
diff --git a/_data/navbars/release-history.yml b/_data/navbars/release-history.yml
index a1dfc709..c9fd9649 100644
--- a/_data/navbars/release-history.yml
+++ b/_data/navbars/release-history.yml
@@ -1,9 +1,11 @@
+# SPDX-License-Identifier: Apache-2.0
+# Copyright (c) 2020 Intel Corporation
+
title: "Release history"
path: /openness_releasenotes/
order: 9
section:
-- title: OpenNESS Release Notes
- path: /openness_releasenotes
- meta_title: OpenNESS Release Notes
- meta_description: OpenNESS Release Notes provides high level system features, issues, and limitations information for OpenNESS.
-
\ No newline at end of file
+ - title: Release Notes
+ path: /openness_releasenotes
+ meta_title: OpenNESS Release Notes
+ meta_description: OpenNESS Release Notes provides high level system features, issues, and limitations information for OpenNESS.
diff --git a/_includes/breadcrumbs.html b/_includes/breadcrumbs.html
index d8b56853..19d18d64 100644
--- a/_includes/breadcrumbs.html
+++ b/_includes/breadcrumbs.html
@@ -1,3 +1,8 @@
+
+
{%- assign pagePath = page.path | remove: ".md" | prepend: "/" -%}
{%- for breadcrumb in include.section -%}
{%- if breadcrumb.section -%}
diff --git a/_includes/footer.html b/_includes/footer.html
index 1cb6e395..5e3d20a8 100644
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -1,3 +1,8 @@
+
+