Skip to content
This repository was archived by the owner on May 27, 2022. It is now read-only.

Commit af8839b

Browse files
krishnajskrishnajs
authored
Merge pull request #61 from open-ness/openness_release_2012
Openness release 2012
2 parents 06dae26 + 736e485 commit af8839b

File tree

212 files changed

+3379
-1547
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

212 files changed

+3379
-1547
lines changed

‎.gitignore

+2
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,5 @@ Gemfile.lock
44
_config.yml
55
_site/
66
*.pdf
7+
.history/doc/overview_20201212222334.md
8+
.history/doc/overview_20201212223809.md

‎README.md

+50-45
Large diffs are not rendered by default.

‎_data/navbars/applications-onboarding.yml

+7-2
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
title: "Application Onboarding"
55
path: /applications-onboard/
6-
order: 2
6+
order: 3
77
section:
88
- title: Network Edge Applications Onboarding
99
path: /doc/applications-onboard/network-edge-applications-onboarding
@@ -20,10 +20,15 @@ section:
2020
meta_title: Edge Application Agent (EAA)
2121
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.
2222

23+
- title: Certificate Signing
24+
path: /doc/applications-onboard/openness-certsigner
25+
meta_title: Certificate Signing
26+
meta_description: Each application that needs the TLS authentication certificate should generate it using the Certificate Signer by sending a CSR via Certificate Requester
27+
2328
- title: Interface Service
2429
path: /doc/applications-onboard/openness-interface-service
2530
meta_title: OpenNESS Applications Onboard - OpenNESS Interface Service
26-
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.
31+
meta_description: OpenNESS Interface service is an application running in Kubernetes pod on every node of OpenNESS Kubernetes cluster and provides OVS bridge, enabling external traffic scenarios.
2732

2833
- title: VM support in OpenNESS for Network Edge
2934
path: /doc/applications-onboard/openness-network-edge-vm-support

‎_data/navbars/building-blocks.yml

+100
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,100 @@
1+
# SPDX-License-Identifier: Apache-2.0
2+
# Copyright (c) 2020 Intel Corporation
3+
4+
title: "Building Blocks"
5+
path: /building-blocks/
6+
order: 2
7+
section:
8+
- title: Data Plane
9+
path:
10+
section:
11+
- title: Inter-App Communication
12+
path: /doc/building-blocks/dataplane/openness-interapp
13+
meta_title: Inter-App Communication Support in OpenNESS
14+
meta_description: OpenNESS provides Inter-App Communication support for Network edge modes of OpenNESS.
15+
16+
- title: OVN/OVS
17+
path: /doc/building-blocks/dataplane/openness-ovn
18+
meta_title: OpenNESS Support for OVS as Dataplane with OVN
19+
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.
20+
21+
- title: Userspace CNI
22+
path: /doc/building-blocks/dataplane/openness-userspace-cni
23+
meta_title: OpenNESS Userspace CNI, Setup Userspace CNI
24+
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.
25+
26+
- title: "Enhanced Platform Awareness"
27+
path:
28+
section:
29+
- title: Hugepage Support
30+
path: /doc/building-blocks/enhanced-platform-awareness/openness-hugepage
31+
meta_title: OpenNESS Enhanced Platform Awareness - Hugepage Support on OpenNESS
32+
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.
33+
34+
- title: Node Feature Discovery Support
35+
path: /doc/building-blocks/enhanced-platform-awareness/openness-node-feature-discovery
36+
meta_title: Enhanced Platform Awareness - Node Feature Discovery Support in OpenNESS
37+
meta_description: OpenNESS Node Feature Discovery is one of the Intel technologies that supports targeting of intelligent configuration and capacity consumption of platform capabilities.
38+
39+
- title: Multiple Interface And PCIe SRIOV Support
40+
path: /doc/building-blocks/enhanced-platform-awareness/openness-sriov-multiple-interfaces
41+
meta_title: Enhanced Platform Awareness - Multiple Interface And PCIe SRIOV Support in OpenNESS
42+
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.
43+
44+
- title: Dedicated CPU Core
45+
path: /doc/building-blocks/enhanced-platform-awareness/openness-dedicated-core
46+
meta_title: Enhanced Platform Awareness - Dedicated CPU Core for Workload Support in OpenNESS
47+
meta_description: Multi-core COTS platforms are typical in any cloud or Cloudnative deployment. Parallel processing on multiple cores helps achieve better density.
48+
49+
- title: BIOS and Firmware Configuration
50+
path: /doc/building-blocks/enhanced-platform-awareness/openness-bios
51+
meta_title: BIOS and Firmware Configuration on OpenNESS Platform
52+
meta_description: BIOS and Firmware are the fundamental platform configurations of a typical Commercial off-the-shelf (COTS) platform.
53+
54+
- title: FPGA Support
55+
path: /doc/building-blocks/enhanced-platform-awareness/openness-fpga
56+
meta_title: FPGA in OpenNESS - Programming, Resource Allocation and Configuration
57+
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.
58+
59+
- title: Intel® vRAN Dedicated Accelerator ACC100
60+
path: /doc/building-blocks/enhanced-platform-awareness/openness-acc100
61+
meta_title: Intel® vRAN Dedicated Accelerator ACC100
62+
meta_description: Using ACC100 eASIC in OpenNESS, Resource Allocation, and Configuration
63+
64+
- title: Intel® Movidius™ Myriad™ X HDDL Support
65+
path: /doc/building-blocks/enhanced-platform-awareness/openness_hddl
66+
meta_title: Intel® Movidius™ Myriad™ X HDDL Solution in OpenNESS
67+
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.
68+
69+
- title: Visual Compute Accelerator Card - Analytics (VCAC-A)
70+
path: /doc/building-blocks/enhanced-platform-awareness/openness-vcac-a
71+
meta_title: Visual Compute Accelerator Card - Analytics (VCAC-A)
72+
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.
73+
74+
- title: Topology Manager Support
75+
path: /doc/building-blocks/enhanced-platform-awareness/openness-topology-manager
76+
meta_title: Topology Manager Support in OpenNESS, Resource Locality Awareness
77+
meta_description: Topology Manager is a solution permitting k8s components like CPU Manager and Device Manager, to coordinate the resources allocated to a workload.
78+
79+
- title: Resource Management Daemon
80+
path: /doc/building-blocks/enhanced-platform-awareness/openness-rmd
81+
meta_title: Cache Allocation for Containers with Resource Management Daemon (RMD)
82+
meta_description: Intel® Resource Director Technology (Intel® RDT) provides visibility and control over how shared resources such as last-level cache (LLC) and memory bandwidth are used by applications, virtual machines (VMs), and containers.
83+
84+
- title: Telemetry support in OpenNESS
85+
path: /doc/building-blocks/enhanced-platform-awareness/openness-telemetry
86+
meta_title: Telemetry support in OpenNESS
87+
meta_description: OpenNESS supports platform and application telemetry allowing users to retrieve information about the platform, the underlying hardware, cluster and applications deployed.
88+
89+
- title: Kubernetes Dashboard in OpenNESS
90+
path: /doc/building-blocks/enhanced-platform-awareness/openness-kubernetes-dashboard
91+
meta_title: Kubernetes Dashboard in OpenNESS
92+
meta_description: OpenNESS supports Kubernetes Dashboard that can be used to inspect and manage Kubernetes cluster.
93+
94+
- title: Multi-Cluster Orchestration
95+
path:
96+
section:
97+
- title: Edge Multi-Cluster Orchestrator (EMCO)
98+
path: /doc/building-blocks/emco/openness-emco
99+
meta_title: Edge Multi-Cluster Orchestrator
100+
meta_description: Geo-Distributed multiple clusters application orchestration.

‎_data/navbars/cloud-adapters.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
title: "Cloud Adapters"
55
path: /cloud-adapters/
6-
order: 8
6+
order: 6
77
section:
88
- title: AWS Greengrass
99
path: /doc/cloud-adapters/openness_awsgreengrass

‎_data/navbars/core-network-4G-5G.yml

-21
This file was deleted.

‎_data/navbars/dataplane.yml

-21
This file was deleted.

‎_data/navbars/devkits.yml

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# SPDX-License-Identifier: Apache-2.0
2+
# Copyright (c) 2020 Intel Corporation
3+
4+
title: "Development Kits"
5+
path: /devkits/
6+
order: 7
7+
section:
8+
- title: OpenNESS Development Kit for Microsoft Azure
9+
path: /doc/devkits/openness-azure-devkit
10+
meta_title: OpenNESS Development Kit for Microsoft Azure
11+
meta_description: This devkit supports the use of OpenNESS in cloud solutions. It leverages the Microsoft Azure Stack for OpenNESS deployment.

‎_data/navbars/edge-applications.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
title: "Edge Applications"
55
path: /applications/
6-
order: 7
6+
order: 5
77
section:
88
- title: Application Development & Porting Guide
99
path: /doc/applications/openness_appguide

‎_data/navbars/enhanced-platform-awareness.yml

-66
This file was deleted.

‎_data/navbars/introduction.yml

+6-1
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,14 @@
22
# Copyright (c) 2020 Intel Corporation
33

44
title: "Introduction"
5-
path: /architecture/
5+
path: /introduction/
66
order: 0
77
section:
8+
- title: OpenNESS Overview
9+
path: /doc/overview
10+
meta_title: OpenNESS Overview
11+
meta_description: OpenNESS is an edge computing software toolkit that enables highly optimized and performant edge platforms to on-board and manage applications and network functions with cloud-like agility across any type of network.
12+
813
- title: OpenNESS Architecture & Solution Overview
914
path: /doc/architecture
1015
meta_title: OpenNESS Architecture And Solution Overview

‎_data/navbars/radio-access-network.yml

-11
This file was deleted.

‎_data/navbars/reference-architectures.yml

+42
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
# SPDX-License-Identifier: Apache-2.0
2+
# Copyright (c) 2020 Intel Corporation
3+
4+
title: "Reference Architectures"
5+
path: /reference-architectures/
6+
order: 4
7+
section:
8+
- title: Core Network
9+
path:
10+
section:
11+
- title: Evolved Packet Core (EPC)
12+
path: /doc/reference-architectures/core-network/openness_epc
13+
meta_title: Edge Cloud Deployment with 3GPP 4G LTE CUPS of EPC
14+
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.
15+
16+
- title: 5G Non-Stand Alone (NSA)
17+
path: /doc/reference-architectures/core-network/openness_5g_nsa
18+
meta_title: Edge Cloud Deployment with 3GPP 5G Non Stand Alone
19+
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.
20+
21+
- title: Next-Gen Core (NGC)
22+
path: /doc/reference-architectures/core-network/openness_ngc
23+
meta_title: Edge Cloud Deployment with 3GPP 5G Stand Alone
24+
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.
25+
26+
- title: User Plane Function (UPF)
27+
path: /doc/reference-architectures/core-network/openness_upf
28+
meta_title: User Plane Function (UPF)
29+
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.
30+
31+
- title: Radio Access Network
32+
path:
33+
section:
34+
- title: OpenNESS Radio Access Network
35+
path: /doc/reference-architectures/ran/openness_ran
36+
meta_title: OpenNESS Radio Access Network is the Edge of Wireless Network
37+
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.
38+
39+
- title: O-RAN Front Haul Sample Application in OpenNESS
40+
path: /doc/reference-architectures/ran/openness_xran
41+
meta_title: 5GNR FlexRAN Front Haul functional units deployment with OpenNESS based on O-RAN specifications at the Network Edge
42+
meta_description: 5GNR FlexRAN Front Haul functional units deployment with OpenNESS based on O-RAN specifications at the Network Edge.

‎_data/navbars/release-history.yml

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
# Copyright (c) 2020 Intel Corporation
33

44
title: "Release history"
5-
path: /openness_releasenotes/
6-
order: 9
5+
path: /release-notes/
6+
order: 8
77
section:
88
- title: Release Notes
99
path: /openness_releasenotes

0 commit comments

Comments
 (0)