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.

Sign up for GitHub

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

support application resource requirements in application profiles #110

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

support application resource requirements in application profiles #110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 15 additions & 0 deletions documentation/API proposals/APIScopeEnhancement_Application_Profiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# API Scope Enhancement

| **Field** | Description |
| ---- | ----- |
| API name | [Application Profiles](https://github.com/camaraproject/ConnectivityInsights) |
| New API name | Application Profiles |
| Scope Enhancement owner | Verizon |
| Scope Enhancement summary | Application profiles allows application developers to share all the information about their application which would be relevant for network CAMARA APIs related decision making. As part of initial scope within connectivity insights, the application profiles API only accepted input of network quality thresholds. Now based on the requirements as agreed in Edge Cloud API, plan is to extend this to accept resource requirements of the application for deployment of the application in edge cloud zone. <br> Also propose that we should plan for creating a new repo to maintain application profiles API rather than it being within connectivity insights as multiple APIs will be utilizing this API.|
| Technical viability | NA
| Commercial viability | NA|
| YAML code available? | YES |
| Validated in lab/productive environments? | a slight variation of this is available in Verizon's implementation of edge discovery service |
| Validated with real customers? | Yes|
| Validated with operators? |Yes |
| Supporters in API Backlog Working Group | Verizon. Discussed and agreed in Edge Cloud API. Need to get formal commitment. |