Support atomic transactions

Registered by Hiroaki Kobayashi

Summary
========

Support atomic transactions for lease.

Problem description
================

In case of a failure of lease, the environment should be reverted back to pre-lease state.
e.g. reverting lease state[3], removing corresponding aggregates.

Use Cases
---------------
- As Wei, I want to receive an appropriate error message in case the a RUR is not
  successful. In case of a failure of RUR I want the environment to be reverted back to
  pre-RUR state. In other words, RUR transaction should be Atomic. In case of RUR failure,
  the error message should contain sufficient information such that user can take actions
  to modify the RUR. (Capacity management user story [2])

Proposed change
==============

TBD

Alternatives
-----------------
TBD

Data model impact
--------------------------
TBD

REST API impact
------------------------
TBD

Security impact
----------------------
TBD

Notifications impact
----------------------------
TBD

Other end user impact
--------------------------------
TBD

Performance impact
-----------------------------
None.

Other deployer impact
--------------------------------
TBD

Developer impact
---------------------------
TBD

Dependencies
===========

TBD

Testing
======
TBD

Documentation impact
==================
TBD

References
=========

[1] https://github.com/openstack/nova-specs/blob/master/specs/pike-template.rst
[2] https://github.com/openstack/openstack-user-stories/blob/master/user-stories/proposed/capacity-management.rst
[3] https://blueprints.launchpad.net/blazar/+spec/lease-state

Note: this form is based on the nova-specs template[1].

Blueprint information

Status:
Complete
Approver:
Masahito Muroi
Priority:
Low
Drafter:
Hiroaki Kobayashi
Direction:
Needs approval
Assignee:
Masahito Muroi
Definition:
Obsolete
Series goal:
Accepted for rocky
Implementation:
Not started
Milestone target:
None
Completed by
Pierre Riteau

Related branches

Sprints

Whiteboard

Update reference [2] to https://github.com/openstack/development-proposals/blob/master/development-proposals/proposed/capacity-management.rst

From the discussion at Dublin PTG, the atomic transaction is already achieved by the state-machine BP. If there is a situation where the state-machine doesn't help atomic transaction, make the BP higher priority. https://blueprints.launchpad.net/blazar/+spec/state-machine

Stein PTG: this should be already handled by the state machine.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.