-
Notifications
You must be signed in to change notification settings - Fork 51
Update README.MD to reflect new folder structure #130
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
Open
Kevsy
wants to merge
6
commits into
main
Choose a base branch
from
Kevsy-patch-8
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
7990a56
Update README.MD to reflect new folder structure
Kevsy 781f6b5
Rename README.MD to README.md
Kevsy b5e0dde
Changed resource management description
Kevsy 31957ed
Update code/API_definitions/README.md
Kevsy 7ee6aa1
Update README.md
Kevsy fda259d
Update README.md
Kevsy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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 site with the shortest network path to an end user terminal,find out which is the optimal Edge site for your specifc application, register your Edge-hosted application endpoints for rapid connectivity to the optimal Edge site. | ||
|
|
||
| Workload Orchestration | ||
| Lifecycle management of the Edge resources and servers for your applications | ||
|
|
||
| # Resource Management | ||
| Information about the resources (compute, storage, networking etc) at a given Edge site | ||
|
|
||
| # Traffic Influence | ||
| Influence traffic routing to ensure optimal network perfromance based on user mobility, application demand, best edge site. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.