Difference between revisions of "MappingOfUseCasesFeaturesRequirementsAndUserStories"
Line 31: | Line 31: | ||
* [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Containers Containers] | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Containers Containers] | ||
* [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Administration_features Administration features] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multi_operator_scenarios Multi operator scenarios] | ||
====[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Universal_customer_premise_equipment_.28uCPE.29_for_Enterprise_Network_Services Universal customer premise equipment (uCPE) for Enterprise Network Services]==== | ====[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Universal_customer_premise_equipment_.28uCPE.29_for_Enterprise_Network_Services Universal customer premise equipment (uCPE) for Enterprise Network Services]==== | ||
Line 37: | Line 39: | ||
* [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
* [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Administration_features Administration features] | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Unmanned_Aircraft_Systems_.28Drones.29 Unmanned Aircraft Systems (Drones)]==== | ||
+ | It is not really clear what functionalities are needed from the infrastructure, but based on my assumptions: | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Elementary_operations_on_one_site Elementary operations on one site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Containers Containers] | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Cloud_Storage_Gateway_-_Storage_at_the_Edge Cloud Storage Gateway - Storage at the Edge]=== | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Elementary_operations_on_one_site Elementary operations on one site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Administration_features Administration features] | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Open_Caching_-_stream.2Fstore_data_at_the_edge Open Caching - stream/store data at the edge]=== | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Elementary_operations_on_one_site Elementary operations on one site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Administration_features Administration features] | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Smart_City_as_Software-Defined_closed-loop_system 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: | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Elementary_operations_on_one_site Elementary operations on one site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Containers Containers] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Administration_features Administration features] | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Augmented_Reality_--_Sony_Gaming_Network Augmented Reality -- Sony Gaming Network]=== | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Elementary_operations_on_one_site Elementary operations on one site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Administration_features Administration features] | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Analytics.2Fcontrol_at_the_edge Analytics/control at the edge]=== | ||
+ | The use case is not developed enough to figure out. | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Manage_retail_chains_-_chick-fil-a Manage retail chains - chick-fil-a]=== | ||
+ | The use case is not developed enough to figure out. | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Smart_Home Smart Home]=== | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Elementary_operations_on_one_site Elementary operations on one site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Data_Collection_-_Smart_cooler.2Fcold_chain_tracking Data Collection - Smart cooler/cold chain tracking]=== | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Elementary_operations_on_one_site Elementary operations on one site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Use_of_a_remote_site Use of a remote site] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Multiple_cloud_stacks Multiple cloud stacks] | ||
+ | |||
+ | ===[https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#VPN_Gateway_Service_Delivery VPN Gateway Service Delivery]=== | ||
+ | The use case is not developed enough to figure out. | ||
===Features=== | ===Features=== |
Revision as of 09:31, 21 December 2018
Contents
- 1 Mapping of Use Cases, Features, Requirements and User Stories
- 1.1 Intro
- 1.2 Requirement types
- 1.3 Relationship of all of these
- 1.4 Mapping of all of these
- 1.4.1 Use cases
- 1.4.2 Cloud Storage Gateway - Storage at the Edge
- 1.4.3 Open Caching - stream/store data at the edge
- 1.4.4 Smart City as Software-Defined closed-loop system
- 1.4.5 Augmented Reality -- Sony Gaming Network
- 1.4.6 Analytics/control at the edge
- 1.4.7 Manage retail chains - chick-fil-a
- 1.4.8 Smart Home
- 1.4.9 Data Collection - Smart cooler/cold chain tracking
- 1.4.10 VPN Gateway Service Delivery
- 1.4.11 Features
- 1.4.11.1 Elementary operations on one site
- 1.4.11.2 Use of a remote site
- 1.4.11.3 Collaboration between edge cloud instances
- 1.4.11.4 Network unreliability
- 1.4.11.5 Containers
- 1.4.11.6 Automatic scheduling between edge cloud instances
- 1.4.11.7 Administration features
- 1.4.11.8 Multiple cloud stacks
- 1.4.11.9 Multi operator scenarios
- 1.4.12 Requirements
- 1.4.12.1 An edge cloud site should be aware of its location
- 1.4.12.2 Discovering of data sources
- 1.4.12.3 Registering for synchronisation
- 1.4.12.4 Advertise metadata data source service
- 1.4.12.5 User management data source side
- 1.4.12.6 User management data receiver side
- 1.4.12.7 RBAC data source side
- 1.4.12.8 RBAC data receiver side
- 1.4.12.9 VM images source side
- 1.4.12.10 VM images receiver side
- 1.4.12.11 Flavors source side
- 1.4.12.12 Flavors receiver side
- 1.4.12.13 Projects source side
- 1.4.12.14 Projects receiver side
- 1.4.12.15 Quotas source side
- 1.4.12.16 Quotas receiver side
- 1.4.12.17 Progress monitoring
- 1.4.12.18 Operability data aggregation data provider part
- 1.4.12.19 Operability data aggregation data aggregator part
- 1.4.12.20 Remote control controlling part
- 1.4.12.21 Remote control receiving part
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.
Requirement types
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.)
Mapping of all of these
Use cases
This section shows which Features are implementing the specific Use cases
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:
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
Data Collection - Smart cooler/cold chain tracking
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:
Administration features
Requirements implementing this feature:
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:
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:
User management data receiver side
MVP User Stories implementing this requirement:
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:
VM images receiver side
MVP User Stories implementing this requirement:
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:
Projects receiver side
MVP User Stories implementing this requirement:
Quotas source side
MVP User Stories implementing this requirement:
Quotas receiver side
MVP User Stories implementing this requirement:
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:
Remote control receiving part
MVP User Stories implementing this requirement: