Update and rename Edge.Cloud.Lifecycle.Management.User.Story.md to Ed…#402
Update and rename Edge.Cloud.Lifecycle.Management.User.Story.md to Ed…#402JoseMConde wants to merge 1 commit intomainfrom
Conversation
…geApplicationManagement_User_Story.md
JoseMConde
requested review from
FabrizioMoggio,
Kevsy,
crissancas,
gainsley,
gunjald,
maheshc01 and
seralogar
as code owners
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports MegaLinter is graciously provided by |
| |MNO|Communications Service Provider|API Publisher | | ||
| |User Client(UC)|API Consumer|API Requester | | ||
|
|
||
| Note: the role of Edge Service Provider may be played by either the MNO or Cloud Service Providers (Hyperscalers). |
There was a problem hiding this comment.
Can there be only two edge service providers i.e., MNO and/or Hyperscalers? Or there may be more and we could express it by mentioning them as example. That is e.g., MNO, Hyperscalers etc
There was a problem hiding this comment.
Thanks @gunjald!! I will mention them as an example.
|
@camaraproject/edge-cloud_codeowners any other comment?? |
| |Step 6|The AP may request updated information of existing app instances of a given app. Possible status for app instantiation includes "ready" also information for endpoint info is provided for the app instance| O | | ||
| |Step 7|App instance may provide service for end users | O | | ||
| |Step 8|The AP request termination of one app instance (optionally all app instances in a given region) | M | | ||
| |Step 9|The OP validates the request (terminates with a notification to the UE if content is not valid e.g. given appId does not exist)| M| |
There was a problem hiding this comment.
Earlier the term used was ESP and here the term used is OP.
It may confuse reader, and OP is not defined in the roles table.
My suggestion is to add OP at the top table or change it to ESP.
There was a problem hiding this comment.
Is edge service provider (ESP) being the edge cloud orchestrator or is it substitute for operator platform?
| |Step 7|App instance may provide service for end users | O | | ||
| |Step 8|The AP request termination of one app instance (optionally all app instances in a given region) | M | | ||
| |Step 9|The OP validates the request (terminates with a notification to the UE if content is not valid e.g. given appId does not exist)| M| | ||
| |Step 10|The OP response to the AP and starts the termination of the app instance, moving its status to terminating| M| |
There was a problem hiding this comment.
Same comment here as above.
| |Step 8|The AP request termination of one app instance (optionally all app instances in a given region) | M | | ||
| |Step 9|The OP validates the request (terminates with a notification to the UE if content is not valid e.g. given appId does not exist)| M| | ||
| |Step 10|The OP response to the AP and starts the termination of the app instance, moving its status to terminating| M| | ||
| |Ends when|The UE connects to the EAS| M | |
There was a problem hiding this comment.
The term User Client (UC) is present in roles table, but UE is not.
User Client is not used in whole user story.
My suggestion is to change the UC in roles table to UE.
3 participants
What type of PR is this?
What this PR does / why we need it:
Update User Story file.
Which issue(s) this PR fixes:
Fixes #399
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.