cleanup scheduler tasks in resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
High
|
Pavlo Shchelokovskyy |
Bug Description
from: https:/
TODO cleanup scheduler tasks in resources: some resources are using scheduler logic directly in the handle_* methods and check_methods. Moving away from this would make transition later on.
This also includes passing rich complex objects between handle_<action> and check_<
List of resource methods to change:
Server.
Server.
Server.
InstanceGro
SwiftSignal
WaitConditi
WaitConditi
NeutronReso
Pool.
(pas-ha) I will take the below resources, may be also refactor volume ones to some base class and AWS and OS subclasses, in separate namespeces
Volume.
VolumeAttac
VolumeAttac
VolumeAttac
Volume.resize (DONE)
(patch on review) security groups rules create/
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Pavlo Shchelokovskyy (pshchelo) |
milestone: | none → kilo-1 |
Changed in heat: | |
milestone: | kilo-1 → kilo-2 |
Changed in heat: | |
milestone: | kilo-2 → kilo-3 |
Changed in heat: | |
milestone: | kilo-3 → kilo-rc1 |
description: | updated |
Changed in heat: | |
milestone: | kilo-rc1 → liberty-1 |
Changed in heat: | |
milestone: | liberty-1 → liberty-2 |
Changed in heat: | |
assignee: | Pavlo Shchelokovskyy (pshchelo) → Steve Baker (steve-stevebaker) |
Changed in heat: | |
assignee: | Steve Baker (steve-stevebaker) → Pavlo Shchelokovskyy (pshchelo) |
Changed in heat: | |
milestone: | liberty-2 → liberty-3 |
Changed in heat: | |
milestone: | liberty-3 → next |
Changed in heat: | |
status: | In Progress → Triaged |
IMO this must be removed only when we have the whole infrastructure of workers running in separate processes/threads in place, when each worker processes a given resource exclusively until completion. Otherwise on current architecture we will penalize performance greatly.