Jump to: navigation, search

Difference between revisions of "MappingOfUseCasesFeaturesRequirementsAndUserStories"

(→‎[User management data source side https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#User_management_data_source_side])
Line 14: Line 14:
  
 
===MVP User Stories===
 
===MVP User Stories===
−
During the 2nd Denver PTG we got the feedback that it would be nice to have an architecture description for a [https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures 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 [https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#User_Stories MVP User Stories].
+
During the 2nd Denver PTG we got the feedback that it would be nice to have an architecture description for a [https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures 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 [https://storyboard.openstack.org/#!/worklist/539 MVP User Stories] and track them in Storyboard.
  
 
==Relationship of all of these==
 
==Relationship of all of these==
Line 31: Line 31:
 
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Discovering_of_data_sources Discovering of data sources]====
 
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Discovering_of_data_sources Discovering of data sources]====
 
MVP User Stories implementing this requirement:
 
MVP User Stories implementing this requirement:
−
* [https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#User_Story_1 User Story 1]?
+
* [https://storyboard.openstack.org/#!/story/2004527 Centralized Control Plane]?
−
* [https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#User_Story_2 User Story 2]?
+
* [https://storyboard.openstack.org/#!/story/2004528 Single API endpoint]?
  
 
=====Open Questions=====
 
=====Open Questions=====
Line 47: Line 47:
 
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#User_management_data_source_side User management data source side]====
 
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#User_management_data_source_side User management data source side]====
 
MVP User Stories implementing this requirement:
 
MVP User Stories implementing this requirement:
−
* None, as the Keystone requirements are not formulated as user stories
+
* [https://storyboard.openstack.org/#!/story/2004530 Distributed Control Plane - Identity]
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#User_management_data_receiver_side User management data receiver side]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004530 Distributed Control Plane - Identity]
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#RBAC_data_source_side RBAC data source side]====
 +
MVP User Stories implementing this requirement:
 +
* None?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#RBAC_data_receiver_side RBAC data receiver side]====
 +
MVP User Stories implementing this requirement:
 +
* None?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#VM_images_source_side VM images source side]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004531 On Demand Image Distribution - Pull Model]
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#VM_images_receiver_side VM images receiver side]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004531 On Demand Image Distribution - Pull Model]
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Flavors_source_side Flavors source side]====
 +
MVP User Stories implementing this requirement:
 +
* None?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Flavors_receiver_side Flavors receiver side]====
 +
MVP User Stories implementing this requirement:
 +
* None?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Projects_source_side Projects source side]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004530 Distributed Control Plane - Identity]
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Projects_receiver_side Projects receiver side]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004530 Distributed Control Plane - Identity]
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Quotas_source_side Quotas source side]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004530 Distributed Control Plane - Identity] ?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Quotas_receiver_side Quotas receiver side]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004530 Distributed Control Plane - Identity] ?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Progress_monitoring Progress monitoring]====
 +
MVP User Stories implementing this requirement:
 +
* None?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Operability_data_aggregation_data_provider_part  Operability data aggregation data provider part]====
 +
MVP User Stories implementing this requirement:
 +
* None?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Operability_data_aggregation_data_aggregator_part  Operability data aggregation data aggregator part]====
 +
MVP User Stories implementing this requirement:
 +
* None?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Remote_control_controlling_part  Remote control controlling part]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004528 Single API endpoint] ?
 +
 
 +
====[https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Remote_control_receiving_part  Remote control receiving part]====
 +
MVP User Stories implementing this requirement:
 +
* [https://storyboard.openstack.org/#!/story/2004528 Single API endpoint] ?

Revision as of 09:12, 18 December 2018

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: RequirementTypeRelations.png

(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

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

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:

Retrieved from "https://wiki.openstack.org/w/index.php?title=MappingOfUseCasesFeaturesRequirementsAndUserStories&oldid=167331"