Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.MD to reflect new folder structure #130

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 0 additions & 20 deletions code/API_definitions/README.MD

This file was deleted.

13 changes: 13 additions & 0 deletions code/API_definitions/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
The Edge Cloud suite of APIs is split into 4 categories, based on the intents listed [here](https://github.com/camaraproject/EdgeCloud/blob/main/documentation/SupportingDocuments/Harmonisation%20of%20APIs/describing%20and%20harmonising%20the%20Edge%20APIs.md).

# Discovery
Discover the Edge Cloud Zone with the shortest network path to an end user terminal, find out which is the optimal Edge Cloud Zone for your specifc application, register your Edge-hosted application endpoints for rapid connectivity to the optimal Edge Cloud Zone.

# Workload Orchestration
Lifecycle management of the Edge resources and servers for your applications

# Resource Management
Management (CRUD) of the edge resources by the application providers for the consumption by edge applications.

# Traffic Influence
Influence traffic routing to ensure optimal network performance based on user mobility, application demand, optimal Edge Cloud Zone.