Difference between revisions of "MappingOfUseCasesFeaturesRequirementsAndUserStories"
Line 23: | Line 23: | ||
==Mapping of all of these== | ==Mapping of all of these== | ||
+ | ===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: | ||
+ | * [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/Edge_Computing_Group/Use_Cases#Universal_customer_premise_equipment_.28uCPE.29_for_Enterprise_Network_Services Universal customer premise equipment (uCPE) for Enterprise Network Services]==== | ||
+ | Features implementing this use case: | ||
+ | * [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] | ||
+ | |||
+ | ===Features=== | ||
+ | This section shows which Requirements are implementing the specific Features | ||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Elementary_operations_on_one_site Elementary operations on one site]==== | ||
+ | Requirements implementing this feature: | ||
+ | * None, as these are already available | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Use_of_a_remote_site Use of a remote site]==== | ||
+ | Requirements implementing this feature: | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Discovering_of_data_sources Discovering of data sources] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Registering_for_synchronisation Registering for synchronisation] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Advertise_metadata_data_source_service Advertise metadata data source service] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#User_management_data_source_side User management data source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#User_management_data_receiver_side User management data receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#RBAC_data_source_side RBAC data source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#RBAC_data_receiver_side RBAC data receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#VM_images_source_side VM images source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#VM_images_receiver_side VM images receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Flavors_source_side Flavors source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Flavors_source_side Flavors receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Projects_source_side Projects source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Projects_receiver_side Projects receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Quotas_source_side Quotas source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Quotas_receiver_side Quotas receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Progress_monitoring Progress monitoring] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Operability_data_aggregation_data_provider_part Operability data aggregation data provider part] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Operability_data_aggregation_data_aggregator_part Operability data aggregation data aggregator part] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Remote_control_controlling_part Remote control controlling part] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Remote_control_receiving_part Remote control receiving part] | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Collaboration_between_edge_cloud_instances Collaboration between edge cloud instances]==== | ||
+ | Requirements implementing this feature: | ||
+ | * None | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Network_unreliability Network unreliability]==== | ||
+ | Requirements implementing this feature: | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#User_management_data_source_side User management data source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#User_management_data_receiver_side User management data receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#RBAC_data_source_side RBAC data source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#RBAC_data_receiver_side RBAC data receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#VM_images_source_side VM images source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#VM_images_receiver_side VM images receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Flavors_source_side Flavors source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Flavors_source_side Flavors receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Projects_source_side Projects source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Projects_receiver_side Projects receiver side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Quotas_source_side Quotas source side] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Quotas_receiver_side Quotas receiver side] | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Containers Containers]==== | ||
+ | Requirements implementing this feature: | ||
+ | * None | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Automatic_scheduling_between_edge_cloud_instances Automatic scheduling between edge cloud instances]==== | ||
+ | Requirements implementing this feature: | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#An_edge_cloud_site_should_be_aware_of_its_location An edge cloud site should be aware of its location] | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Administration_features Administration features]==== | ||
+ | Requirements implementing this feature: | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Operability_data_aggregation_data_provider_part Operability data aggregation data provider part] | ||
+ | * [https://wiki.openstack.org/wiki/MappingOfUseCasesFeaturesRequirementsAndUserStories#Operability_data_aggregation_data_aggregator_part Operability data aggregation data aggregator part] | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Multiple_cloud_stacks Multiple cloud stacks]==== | ||
+ | Requirements implementing this feature: | ||
+ | * None | ||
+ | |||
+ | ====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Multi_operator_scenarios Multi operator scenarios]==== | ||
+ | Requirements implementing this feature: | ||
+ | * None | ||
+ | |||
===Requirements=== | ===Requirements=== | ||
This section shows which MVP User Stories are implementing the specific Requirements | This section shows which MVP User Stories are implementing the specific Requirements | ||
Line 112: | Line 196: | ||
MVP User Stories implementing this requirement: | MVP User Stories implementing this requirement: | ||
* [https://storyboard.openstack.org/#!/story/2004528 Single API endpoint] ? | * [https://storyboard.openstack.org/#!/story/2004528 Single API endpoint] ? | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 09:48, 18 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 Features
- 1.4.2.1 Elementary operations on one site
- 1.4.2.2 Use of a remote site
- 1.4.2.3 Collaboration between edge cloud instances
- 1.4.2.4 Network unreliability
- 1.4.2.5 Containers
- 1.4.2.6 Automatic scheduling between edge cloud instances
- 1.4.2.7 Administration features
- 1.4.2.8 Multiple cloud stacks
- 1.4.2.9 Multi operator scenarios
- 1.4.3 Requirements
- 1.4.3.1 An edge cloud site should be aware of its location
- 1.4.3.2 Discovering of data sources
- 1.4.3.3 Registering for synchronisation
- 1.4.3.4 Advertise metadata data source service
- 1.4.3.5 User management data source side
- 1.4.3.6 User management data receiver side
- 1.4.3.7 RBAC data source side
- 1.4.3.8 RBAC data receiver side
- 1.4.3.9 VM images source side
- 1.4.3.10 VM images receiver side
- 1.4.3.11 Flavors source side
- 1.4.3.12 Flavors receiver side
- 1.4.3.13 Projects source side
- 1.4.3.14 Projects receiver side
- 1.4.3.15 Quotas source side
- 1.4.3.16 Quotas receiver side
- 1.4.3.17 Progress monitoring
- 1.4.3.18 Operability data aggregation data provider part
- 1.4.3.19 Operability data aggregation data aggregator part
- 1.4.3.20 Remote control controlling part
- 1.4.3.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:
Universal customer premise equipment (uCPE) for Enterprise Network Services
Features implementing this use case:
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: