MAAS only keep the last installation log

Bug #1446916 reported by Andres Rodriguez
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Wishlist
Unassigned

Bug Description

Each time maas deployes a node (or fails to) it records the isntallation log. Next time it is deployed, the log gets deleted. However, MAAS should be able to store eveyr single one of the installation logs.

Tags: oil
Changed in maas:
milestone: none → 1.8.0
tags: added: oil
Changed in maas:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

Missing these logs is block our ability to collect logs for bug 1454469.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

I am trying to think what is the best way to store these logs. We don't have like a notion of an instance id or anything like that. The best thing that we could do maybe is storing the logs as a file on the region based on the time when the deploy log is received from curtin. This means you will need to identify the correct file based on time for your installation log.

/var/log/maas/deploy/node-blah-blah/21_May_2015_16-33-01_install_log.log

Would this work?

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Blake,

What about storing the installation logs on the DB ? I think it would be nice to link each Node Event Log with an installation log. For example:

 Node changed status - From 'Deploying' to 'Deployed' Sat, 16 May. 2015 20:30:39

It would be nice if that event log would have the link to the respective log. In the main page, we can have the latest installation log, but from the event log, we can access the installation log for that installation.

from the events API, we can just simply get all the successful installations and a way to access their log. So if a user was to obtain the log for that installation, they have a list of successful installations (from deploying to deployed) or unsuccessful (from X to failed deployment). THoughts?

Revision history for this message
Gavin Panella (allenap) wrote :

Storing logs on clusters would scale best. Next best would be in the database.

Revision history for this message
Raphaël Badin (rvb) wrote :

Remember that only the region is meant to be "HA"… I think storing them in the DB (compressed) is the way to go here.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

Yeah I agree it should be in the database to allow for HA.

I think Andres is correct we should probably link it to the event log entry for now. I do think in the future maybe seperating a node and an instance might be a good idea.

Raphaël Badin (rvb)
summary: - MAAS should provide access to every installation log recorded
+ MAAS only keep the last installation log
Changed in maas:
milestone: 1.8.0 → 1.9.0
Changed in maas:
importance: High → Wishlist
Changed in maas:
milestone: 1.9.0 → 2.0.0
Changed in maas:
milestone: 2.0.0 → 2.1.0
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Changed in maas:
milestone: 2.1.3 → next
Changed in maas:
status: Triaged → Fix Released
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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