power state changes are not reflected quickly enough in the UI
Bug #1357073 reported by
Andres Rodriguez
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse |
Bug Description
The interval is too long, went through commissioning and it never really displayed the actual status of the machine. INterval should probably be just 1 minute.
src/provisionin
Related branches
lp:~blake-rouse/maas/query-power-on-status-change
- Julian Edwards (community): Approve
-
Diff: 291 lines (+263/-0)4 files modifiedsrc/maasserver/models/__init__.py (+3/-0)
src/maasserver/node_query.py (+108/-0)
src/maasserver/node_status.py (+20/-0)
src/maasserver/tests/test_node_query.py (+132/-0)
Changed in maas: | |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
milestone: | none → 1.7.0 |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Triaged |
Changed in maas: | |
milestone: | 1.7.0 → next |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | next → 1.7.1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
> The interval is too long, went through commissioning and it never
> really displayed the actual status of the machine. INterval should
> probably be just 1 minute.
This should probably not be solved by decreasing the interval. Instead,
those parts of MAAS that are able to infer the power status of a machine
(e.g. where an HTTP request comes in from its IP address) should update
the machine's power status with what they know. Times like commissioning
and deploying are those times when power is most in flux and also when
there's the most activity from which to infer the machine's power
status.
For extra points, we could modify the interval based on the machine's allocated- >deploying- >deployed transition, followed by an ongoing
lifecycle status. An unallocated machine could be checked once every
15-30 minutes, or even less frequently, for example. I think we're most
interested in the power status of machines going through a
ready->
power status of deployed machines, followed by the power status of
machines in other lifecycle states.
For even more points, we may want to actively power off machines in
those lifecycle states where they ought to be dormant.