Introduce Blazar objects
Summary
========
Object is necessary for Blazar in order to provide a defined interface in between the
Manager and DB. The object will have tenancy information so that it should enforce
policies on a safer way. That will also allow us to perform HA easier as it will reduce the DB locking problem, and it will also allow RPC interfaces to define a path for DB upgrades.
See https:/
Problem description
================
TBD
Use Cases
---------------
TBD
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:/
[2] https:/
Note: this form is based on the nova-specs template[1].
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Sylvain Bauza
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- next
- Started by
- Completed by
- Pierre Riteau
Related branches
Related bugs
Sprints
Whiteboard
History:
We can implement HA without this feature. Central core services will give events processing to workers. Central ones will use DB transactions and change event state tile:
with session:
task = session.
task['state'] = TAKEN
And there will be no race conditions here because of transactions.
So this BP on current code state is not worth efforts spent on it. There are lots of other things to do....