Logbook objects, not collections

Registered by Ivan Melnikov on 2014-03-31

It is proposed to stop treating logbook object as collection of smaller objects: LogBook and FlowDetails should be made simple data-transfer objects, not containers for FlowDetails and AtomDetails respectively. Corresponding API should be moved to backends.

Blueprint information

Status:
Started
Approver:
Joshua Harlow
Priority:
High
Drafter:
Ivan Melnikov
Direction:
Needs approval
Assignee:
Joshua Harlow
Definition:
Approved
Series goal:
None
Implementation:
Slow progress
Milestone target:
None
Started by
Joshua Harlow on 2014-08-23

Related branches

Sprints

Whiteboard

Can u explain this in more depth, still unsure what it would mean. Thanks!

I tried to explain what I mean on wiki: https://wiki.openstack.org/wiki/TaskFlow/Persistence/Objects,_not_Collections (same as 'Read full specification' link above).

Thanks, I think I get it.

Gerrit topic: https://review.openstack.org/#q,topic:bp/lb-not-collections,n,z

Updating milestone and approval settings prior to kilo. - dhellmann

Addressed by: https://review.openstack.org/114422
    Initial shift to having backends provide storage impls

Addressed by: https://review.openstack.org/114716
    If not provided create and populate a in-memory backend

Addressed by: https://review.openstack.org/167857
    Optionally do caching/updating of flowdetail in storage

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.