MappingOfUseCasesFeaturesRequirementsAndUserStories

=Mapping of Use Cases, Features, Requirements and User Stories=

Intro
OpenStack Edge Computing Group (ECG) is a collaboration between several actors and it works on the complex problems of edge computing. As a result of this setup the group uses different places and different terms to describe requirements to he different levels of the edge cloud problem domain. This page collects all the different used levels and makes an attempt to describe a linkage between them.

Features
These are high level features of an edge cloud infrastructure described in a way, that they do not assume any technology details on the implementation. These Features are first developed by the FEMDC SIG and were agreed on and after the Dublin PTG Edge Workshop.

Requirements
Requirements of edge cloud implementations based on the Features with an attempt to identify the components within the edge cloud instances.

Use Cases
ECG have a Subgroup to define Use Cases. These use cases are high level business driven Use Cases for the whole edge cloud infrastructure. They describe a problem what could be solved using edge cloud infrastructure without providing any solution proposals.

MVP User Stories
During the 2nd Denver PTG we got the feedback that it would be nice to have an architecture description for a Minimum Viable Product (MVP) edge architecture. This is an architecture which implements no more, than the very basic requirements of an edge cloud architecture. We were lucky to have the Oath team in the room who shared their edge cloud design with us. We agreed to use this as the first MVP architecture. This MVP architecture takes the existing OpenStack as a basis and defines some requirements to specific OpenStack projects. These requirements are formulated as User Stories, therefore we call them MVP User Stories and track them in Storyboard.

Relationship of all of these
In an ideal world it would look like this:

(For some reasons I was not able to upload the pptx source of this figure to here, so if anyone would like to make modifications on it I'm (csatari) happy to email it over.)

Use cases
This section shows which Features are implementing the specific Use cases ====[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Mobile_service_provider_5G.2F4G_virtual_RAN_deployment_and_Edge_Cloud_B2B2X. Mobile service provider 5G/4G virtual RAN deployment and Edge Cloud B2B2X.]==== Features implementing this use case:
 * Elementary operations on one site
 * Use of a remote site
 * Containers
 * Multiple cloud stacks
 * Administration features
 * Multi operator scenarios

====Universal customer premise equipment (uCPE) for Enterprise Network Services==== Features implementing this use case:
 * Elementary operations on one site
 * Use of a remote site
 * Multiple cloud stacks
 * Administration features

Unmanned Aircraft Systems (Drones)
It is not really clear what functionalities are needed from the infrastructure, but based on my assumptions:
 * Elementary operations on one site
 * Use of a remote site
 * Containers

Cloud Storage Gateway - Storage at the Edge

 * Elementary operations on one site
 * Use of a remote site
 * Multiple cloud stacks
 * Administration features

Open Caching - stream/store data at the edge

 * Elementary operations on one site
 * Use of a remote site
 * Multiple cloud stacks
 * Administration features

Smart City as Software-Defined closed-loop system
It is not really clear what functionalities are needed from the infrastructure, but based on my assumptions:
 * Elementary operations on one site
 * Use of a remote site
 * Containers
 * Multiple cloud stacks
 * Administration features

Augmented Reality -- Sony Gaming Network

 * Elementary operations on one site
 * Use of a remote site
 * Multiple cloud stacks
 * Administration features

Analytics/control at the edge
The use case is not developed enough to figure out.

Manage retail chains - chick-fil-a
The use case is not developed enough to figure out.

Smart Home

 * Elementary operations on one site
 * Use of a remote site
 * Multiple cloud stacks

Data Collection - Smart cooler/cold chain tracking

 * Elementary operations on one site
 * Use of a remote site
 * Multiple cloud stacks

VPN Gateway Service Delivery
The use case is not developed enough to figure out.

Features
This section shows which Requirements are implementing the specific Features

Elementary operations on one site
Requirements implementing this feature:
 * None, as these are already available

Use of a remote site
Requirements implementing this feature:
 * Discovering of data sources
 * Registering for synchronisation
 * Advertise metadata data source service
 * User management data source side
 * User management data receiver side
 * RBAC data source side
 * RBAC data receiver side
 * VM images source side
 * VM images receiver side
 * Flavors source side
 * Flavors receiver side
 * Projects source side
 * Projects receiver side
 * Quotas source side
 * Quotas receiver side
 * Progress monitoring
 * Operability data aggregation data provider part
 * Operability data aggregation data aggregator part
 * Remote control controlling part
 * Remote control receiving part

Collaboration between edge cloud instances
Requirements implementing this feature:
 * None

Network unreliability
Requirements implementing this feature:
 * User management data source side
 * User management data receiver side
 * RBAC data source side
 * RBAC data receiver side
 * VM images source side
 * VM images receiver side
 * Flavors source side
 * Flavors receiver side
 * Projects source side
 * Projects receiver side
 * Quotas source side
 * Quotas receiver side

Containers
Requirements implementing this feature:
 * None

Automatic scheduling between edge cloud instances
Requirements implementing this feature:
 * An edge cloud site should be aware of its location

Administration features
Requirements implementing this feature:
 * Operability data aggregation data provider part
 * Operability data aggregation data aggregator part

Multiple cloud stacks
Requirements implementing this feature:
 * None

Multi operator scenarios
Requirements implementing this feature:
 * None

Requirements
This section shows which MVP User Stories are implementing the specific Requirements

An edge cloud site should be aware of its location
MVP User Stories implementing this requirement:
 * None

Discovering of data sources
MVP User Stories implementing this requirement:
 * Centralized Control Plane?
 * Single API endpoint?

Open Questions

 * Clarify if the discovery really works (ie.: If there is really no need for any edge site related configuration at installation time)

Registering for synchronisation
MVP User Stories implementing this requirement:
 * None, as the MVP architecture is built on the pull model and the metadata what is pulled is limited to the Keystone and Glance metadata

Advertise metadata data source service
MVP User Stories implementing this requirement:
 * None, as the MVP architecture is built on the pull model and the metadata what is pulled is limited to the Keystone and Glance metadata

User management data source side
MVP User Stories implementing this requirement:
 * Distributed Control Plane - Identity

User management data receiver side
MVP User Stories implementing this requirement:
 * Distributed Control Plane - Identity

RBAC data source side
MVP User Stories implementing this requirement:
 * None?

RBAC data receiver side
MVP User Stories implementing this requirement:
 * None?

VM images source side
MVP User Stories implementing this requirement:
 * On Demand Image Distribution - Pull Model

VM images receiver side
MVP User Stories implementing this requirement:
 * On Demand Image Distribution - Pull Model

Flavors source side
MVP User Stories implementing this requirement:
 * None?

Flavors receiver side
MVP User Stories implementing this requirement:
 * None?

Projects source side
MVP User Stories implementing this requirement:
 * Distributed Control Plane - Identity

Projects receiver side
MVP User Stories implementing this requirement:
 * Distributed Control Plane - Identity

Quotas source side
MVP User Stories implementing this requirement:
 * Distributed Control Plane - Identity ?

Quotas receiver side
MVP User Stories implementing this requirement:
 * Distributed Control Plane - Identity ?

Progress monitoring
MVP User Stories implementing this requirement:
 * None?

Operability data aggregation data provider part
MVP User Stories implementing this requirement:
 * None?

Operability data aggregation data aggregator part
MVP User Stories implementing this requirement:
 * None?

Remote control controlling part
MVP User Stories implementing this requirement:
 * Single API endpoint ?

Remote control receiving part
MVP User Stories implementing this requirement:
 * Single API endpoint ?