Refactor flow of Nailgun objects and make it DRY

Registered by Nikolay Markov

There are a lot of copy-paste in Nailgun handlers (Node/NodeCollection especially) and some spaghetti code dealing with state changing for Cluster, Task, Node etc. Current solution is to move this code into separate class or module to implement 'flow' for these objects.

Blueprint information

Status:
Complete
Approver:
Evgeniy L
Priority:
Medium
Drafter:
Nikolay Markov
Direction:
Approved
Assignee:
Nikolay Markov
Definition:
Approved
Series goal:
Accepted for 5.0.x
Implementation:
Implemented
Milestone target:
milestone icon 5.0
Started by
Nikolay Markov
Completed by
Dmitry Pyzhov

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/nailgun-objects-flow,n,z

Addressed by: https://review.openstack.org/81501
    Cluster object

Addressed by: https://review.openstack.org/81824
    Cluster helpers now in object & tests

Addressed by: https://review.openstack.org/83432
    Initial version of Node object

Addressed by: https://review.openstack.org/84774
    Notification object - preparing for pagination

Addressed by: https://review.openstack.org/86340
    Nailgun base objects autodoc & small refactoring

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.