Skip to content
This repository has been archived by the owner on Jul 31, 2023. It is now read-only.

Commit

Permalink
Merge pull request #13 from open-ness/openness_release_2103
Browse files Browse the repository at this point in the history
Openness release 2103
cjnolan authored Mar 31, 2021

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
2 parents 9e825ba + 56fb4ff commit e1e58d7
Showing 69 changed files with 3,968 additions and 2,255 deletions.
18 changes: 11 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
@@ -6,7 +6,7 @@ Copyright (c) 2019-2020 Intel Corporation
# OpenNESS Quick Start

## <b>Network Edge</b>
### <b>Step 1.</b> Get Hardware &#9658; <b>Step 2.</b> [Getting started](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/network-edge/controller-edge-node-setup.md) &#9658; <b>Step 3.</b> [Applications Onboarding](https://github.com/open-ness/ido-specs/blob/master/doc/applications-onboard/network-edge-applications-onboarding.md)
### <b>Step 1.</b> Get Hardware &#9658; <b>Step 2.</b> [Getting started](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/openness-cluster-setup.md) &#9658; <b>Step 3.</b> [Applications Onboarding](https://github.com/open-ness/ido-specs/blob/master/doc/applications-onboard/network-edge-applications-onboarding.md)

# OpenNESS solution documentation index

@@ -20,10 +20,12 @@ Below is the complete list of OpenNESS solution documentation
## Getting Started - Setup

* [<b>getting-started</b>: Folder containing how to get started with installing and trying OpenNESS Network Edge solutions](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started)
* [<b>openness-experience-kits.md</b>: Overview of the OpenNESS Experience kits that are used to install the Network Edge solutions](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/openness-experience-kits.md)
* [<b>network-edge</b>: Folder containing how to get started with installing and trying OpenNESS Network Edge](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/network-edge)
* [<b>controller-edge-node-setup.md</b>: Started here for installing and trying OpenNESS Network Edge](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/network-edge/controller-edge-node-setup.md)
* [<b>supported-epa.md</b>: List of Silicon and Software EPA that are features that are supported in OpenNESS Network Edge](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/network-edge/supported-epa.md)
* [<b>openness-cluster-setup.md</b>: Getting started here for installing and trying OpenNESS Network Edge](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/openness-cluster-setup.md)
* [<b>converged-edge-experience-kits.md</b>: Overview of the Converged Edge Experience Kits that are used to install the Network Edge solutions](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/converged-edge-experience-kits.md)
* [<b>non-root-user.md</b>: Using the non-root user on the OpenNESS Platform](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/non-root-user.md)
* [<b>offline-edge-deployment.md</b>: Setting up OpenNESS in an air-gapped, offline environment](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/offline-edge-deployment.md)
* [<b>harbor-registry.md</b>: Enabling Harbor Registry service in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/harbor-registry.md)
* [<b>kubernetes-dashboard.md</b>: Installing Kubernetes Dashboard for OpenNESS Network Edge cluster](https://github.com/open-ness/ido-specs/blob/master/doc/getting-started/kubernetes-dashboard.md)

## Application onboarding - Deployment

@@ -57,11 +59,11 @@ Below is the complete list of OpenNESS solution documentation
* [<b>openness-sriov-multiple-interfaces.md</b>: Dedicated Physical Network interface allocation support for Edge Applications and Network Functions](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-sriov-multiple-interfaces.md)
* [<b>openness-dedicated-core.md</b>: Dedicated CPU core allocation support for Edge Applications and Network Functions](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-dedicated-core.md)
* [<b>openness-bios.md</b>: Edge platform BIOS and Firmware and configuration support in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-bios.md)
* [<b>openness-qat.md</b>: Resource allocation & configuration of Intel® QuickAssist Adapter](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-qat.md)
* [<b>openness-fpga.md</b>: Dedicated FPGA IP resource allocation support for Edge Applications and Network Functions](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-fpga.md)
* [<b>openness_hddl.md</b>: Using Intel® Movidius™ Myriad™ X High Density Deep Learning (HDDL) solution in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness_hddl.md)
* [<b>openness-topology-manager.md</b>: Resource Locality awareness support through Topology manager in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-topology-manager.md)
* [<b>openness-vca.md</b>: Visual Compute Accelerator Card - Analytics (VCAC-A)](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-vcac-a.md)
* [<b>openness-kubernetes-dashboard.md</b>: Kubernetes Dashboard in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-kubernetes-dashboard.md)
* [<b>openness-rmd.md</b>: Cache Allocation using Resource Management Daemon(RMD) in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-rmd.md)
* [<b>openness-telemetry</b>: Telemetry Support in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/building-blocks/enhanced-platform-awareness/openness-telemetry.md)

@@ -78,6 +80,8 @@ Below is the complete list of OpenNESS solution documentation
* [<b>openness_appguide.md</b>: How to develop or Port existing cloud application to the Edge cloud based on OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/applications/openness_appguide.md)
* [<b>openness_ovc.md</b>: Open Visual Cloud Smart City reference Application for OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/applications/openness_ovc.md)
* [<b>openness_openvino.md</b>: AI inference reference Edge application for OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/applications/openness_openvino.md)
* [<b>openness_va_services.md</b>: Video Analytics Services for OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/applications/openness_va_services.md)
* [<b>openness_service_mesh.md</b>: Service Mesh support in OpenNESS](https://github.com/open-ness/ido-specs/blob/master/doc/applications/openness_service_mesh.md)

## Cloud Adapters

@@ -155,5 +159,5 @@ Below is the complete list of OpenNESS solution documentation
- DU: Distributed Unit of RAN
- CU: Centralized Unit of RAN
- SBI: Service Based Interfaces
- OEK: OpenNESS Experience Kit
- CEEK: Converged Edge Experience Kits
- IDO: Intel Distribution of OpenNESS
10 changes: 5 additions & 5 deletions _data/navbars/building-blocks.yml
Original file line number Diff line number Diff line change
@@ -71,6 +71,11 @@ section:
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: Intel® QuickAssist Adapter
path: /doc/building-blocks/enhanced-platform-awareness/openness-qat
meta_title: Using Intel® QuickAssist Adapter in OpenNESS - Resource Allocation, and Configuration
meta_description: Intel® QuickAssist Adapter plays a key role in accelerating cryptographic operations in 5G networking.

- title: Topology Manager Support
path: /doc/building-blocks/enhanced-platform-awareness/openness-topology-manager
meta_title: Topology Manager Support in OpenNESS, Resource Locality Awareness
@@ -86,11 +91,6 @@ section:
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.

- title: Kubernetes Dashboard in OpenNESS
path: /doc/building-blocks/enhanced-platform-awareness/openness-kubernetes-dashboard
meta_title: Kubernetes Dashboard in OpenNESS
meta_description: OpenNESS supports Kubernetes Dashboard that can be used to inspect and manage Kubernetes cluster.

- title: Multi-Cluster Orchestration
path:
section:
38 changes: 25 additions & 13 deletions _data/navbars/getting-started.yml
Original file line number Diff line number Diff line change
@@ -5,20 +5,32 @@ title: "Getting Started"
path: /getting-started/
order: 1
section:
- title: OpenNESS Experience Kits
path: /doc/getting-started/openness-experience-kits
- title: OpenNESS Cluster Setup
path: /doc/getting-started/openness-cluster-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: Converged Edge Experience Kits
path: /doc/getting-started/converged-edge-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 mode.

- title: Network Edge
path:
section:
- title: Controller & Edge Node Setup
path: /doc/getting-started/network-edge/controller-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: OpenNESS Offline Deployment
path: /doc/getting-started/offline-edge-deployment
meta_title: OpenNESS Offline Deployment
meta_description: The OpenNESS projects supports a deployment of the solution in an air-gapped, offline environment.

- title: Non-root User in OpenNESS
path: /doc/getting-started/non-root-user
meta_title: The non-root user on the OpenNESS Platform
meta_description: OpenNESS provides a possibility to install all required files on Kubernetes a control plane and nodes with or without root rights.

- title: Harbor Registry Service
path: /doc/getting-started/harbor-registry
meta_title: Harbor Registry Service in OpenNESS
meta_description: Enabling Harbor registry service in OpenNESS

- 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: Kubernetes Dashboard in OpenNESS
path: /doc/getting-started/kubernetes-dashboard
meta_title: Kubernetes Dashboard in OpenNESS
meta_description: OpenNESS supports Kubernetes Dashboard that can be used to inspect and manage Kubernetes cluster.
2 changes: 1 addition & 1 deletion _data/navbars/reference-architectures.yml
Original file line number Diff line number Diff line change
@@ -52,6 +52,6 @@ section:
meta_description: Reference architecture combines wireless and high performance compute for IoT, AI, video and other services.

- title: Converged Edge Reference Architecture for SD-WAN
path: /doc/reference-architectures/openness_sdwan
path: /doc/reference-architectures/cera_sdwan
meta_title: Converged Edge Reference Architecture for SD-WAN
meta_description: OpenNESS provides a reference solution for SD-WAN consisting of building blocks for cloud-native deployments.
2 changes: 1 addition & 1 deletion _includes/header.html
Original file line number Diff line number Diff line change
@@ -36,7 +36,7 @@
<li class="item-137 deeper parent">
<a href="https://github.com/open-ness/specs/tree/master/doc/getting-started" target="_blank" rel="noopener noreferrer">Getting Started</a>
<ul class="nav-child unstyled small" style="display: none;">
<li class="item-138"><a href="https://github.com/open-ness/specs/blob/master/doc/getting-started/network-edge/controller-edge-node-setup.md" target="_blank" rel="noopener noreferrer">OpenNESS Network Edge Getting Started</a></li>
<li class="item-138"><a href="https://github.com/open-ness/specs/blob/master/doc/getting-started/openness-cluster-setup.md" target="_blank" rel="noopener noreferrer">OpenNESS Network Edge Getting Started</a></li>
</ul>
</li>
<li class="item-143"><a href="/docs/">Documentation</a></li>
Loading

0 comments on commit e1e58d7

Please sign in to comment.