MAAS

Add machine deploy timestamp to websocket api

Bug #1899891 reported by Caleb Ellis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Expired
Undecided
Unassigned

Bug Description

We would like to surface the machine deployment time in the UI, likely in the machine list as well as the machine details pages.

Revision history for this message
Lee Trager (ltrager) wrote :

When a machine starts a deployment a ScriptResult is created. There are four fields related to timing:

script_result.created - When the user told MAAS to deploy an operating system
script_result.started - When the deployment actually began
script_result.ended - When Curtin finished installing
script_result.runtime - The time the deployment took to run, not including reboot time.

The UI already gets the ScriptResult for the installation log, you should be able to use the same path.

Changed in maas:
status: New → Incomplete
Björn Tillenius (bjornt)
Changed in maas:
milestone: next → none
Björn Tillenius (bjornt)
Changed in maas:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.