x/development-proposals
Code Issues Proposed changes

Merge "Added unique identifier to each use case/requirements."

Browse Source
This commit is contained in:
Jenkins
2016-11-30 23:19:17 +00:00
committed by Gerrit Code Review
parent f8cc101ff2 071841ec64
commit 853e6c88a7
1 changed files with 25 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
user-stories/proposed/baremetal-service.rst
View File

@@ -69,35 +69,39 @@ Use Cases
User Stories
++++++++++++
* As an Enterprise user, I want to use bare metal machine so that I get
consistent performance not affected by another machine, nor impacted
* BMT001 - As an Enterprise user, I want to use bare metal machine so that I
get consistent performance not affected by another machine, nor impacted
by hypervisor.
* As an Enterprise user, I want to have a secure and clean bare metal machine
deployed no matter who used it before.
* BMT002 - As an Enterprise user, I want to have a secure and clean bare
metal machine deployed no matter who used it before.
* As an Enterprise user, I want to create networks elastically so that I can
use network like I have these networks not affected by other companies.
* BMT003 - As an Enterprise user, I want to create networks elastically so
that I can use network like I have these networks not affected by other
companies.
* As an Enterprise user, I want to back up internal disk of bare metal and
create a snapshot. This can be backed up to an external storage managed by
Cinder.
* BMT004 - As an Enterprise user, I want to back up internal disk of bare
metal and create a snapshot. This can be backed up to an external storage
managed by Cinder.
* As an Enterprise user, I want to use bare metal machine integrated with
block storage service so that I can use external storage service.
* BMT005 - As an Enterprise user, I want to use bare metal machine
integrated with block storage service so that I can use external
storage service.
* As an Enterprise user, I want to see bare metal machine from console log and
operate from console so that I can analyze problems at booting time and so on.
* BMT006 - As an Enterprise user, I want to see bare metal machine from
console log and operate from console so that I can analyze problems at
booting time and so on.
* As an Enterprise user, I want to continue my operation immediately when
a bare metal machine fails without any manual operations such as switchover.
Similar to HA VM user story, The user should not have to design the fail-over
mechanism themselves. The system should monitor and detect bare metal machine
failure and automatically fail-over to a spare bare metal machine.
* BMT007 - As an Enterprise user, I want to continue my operation
immediately when a bare metal machine fails without any manual
operations such as switchover. Similar to HA VM user story, The user
should not have to design the fail-over mechanism themselves. The system
should monitor and detect bare metal machine failure and automatically
fail-over to a spare bare metal machine.
* As an Enterprise user, I want to use a bare metal machine with the network
services such as FWaaS, LBaaS, Security Group, VPNaaS, and connection
to VMs in virtual network(VXLAN) in the same manner of VMs.
* BMT008 - As an Enterprise user, I want to use a bare metal machine with
the network services such as FWaaS, LBaaS, Security Group, VPNaaS, and
connection to VMs in virtual network(VXLAN) in the same manner of VMs.
Usage Scenario Examples
+++++++++++++++++++++++