---------- Forwarded message ----------
From: "sachidananda sahu" <sachi...@gmail.com>
Date: 10-Aug-2017 8:09 AM
Subject: Re: Regarding alarm and metrics in MAAS
To: "Lee Trager" <lee.tra...@canonical.com>
Cc:

Hello Lee, Thanks for your quick response .
I am looking towards maintaining statistics at overall maas level(Total no
of node deployed, total no of node failed in deployment , total no of node
failed in specific event and their cause etc) so that the user can get a
overall idea about maas region controller.



On 10-Aug-2017 5:59 AM, "Lee Trager" <lee.tra...@canonical.com> wrote:

> Could you be more specific about the data you are looking for?
>
> `maas <profile> node-script-result read <system_id> current-installation`
> will give statistics about the installation. You can get a list of all
> machine system_ids with `maas <profile> machines read` To get event log
> data you can use `maas <profile> events query id=<system_id>
>
>
> On Wed, Aug 9, 2017 at 5:01 PM, sachidananda sahu <sachi...@gmail.com>
> wrote:
>
>> Thanks for the detailed info, but all I can see which is only at node
>> level, is there any way to get overall counts, failure counts and
>>  statistics of all nodes ?
>>
>> On 10-Aug-2017 3:26 AM, "Lee Trager" <lee.tra...@canonical.com> wrote:
>>
>>> Anything you can do in the UI you can also do in the using the API/CLI.
>>> To download the current installation log you can use the command
>>>
>>> maas <profile> node-script-result download <system_id>
>>> current-installation
>>>
>>> Similarly you can do the same for commissioning  or testing results
>>> maas <profile> node-script-result download <system_id>
>>> current-commissioning
>>> maas <profile> node-script-result download <system_id> current-testing
>>>
>>> For commissioning and testing results you may want to download a tar
>>> with all results instead of the text
>>> maas <profile> node-script-result download <system_id> current-testing
>>> filetype=tar.xz
>>>
>>> MAAS stores metadata about the result status as status, runtime, and
>>> when installation/commissioning/testing started
>>> maas <profile> node-script-result read <system_id> current-installation
>>>
>>> MAAS also stores historic results which can be viewed with
>>> maas <profile> node-script-results read <system_id>
>>>
>>> Hope that helps!
>>>
>>> Lee
>>>
>>> On Tue, Aug 8, 2017 at 7:29 PM, sachidananda sahu <sachi...@gmail.com>
>>> wrote:
>>>
>>>> Yes Blake, the GUI provides only the node level events(Not at maas
>>>> region level and not overall about all the nodes), but is there any
>>>> directory where it is stored ?
>>>>
>>>> Jeff, you are right.This was my questions intention.
>>>>
>>>> It will be better to get the deployment log of each node in some
>>>> specific directory(may be in /etc/maas/logs/node*
>>>>
>>>> In addition to that it will be nice to have the logs or mantaining
>>>>  statistics at overall maas level(Total no of node deployed, total no of
>>>> node failed in deployment , total no of node failed in specific event and
>>>> their cause etc) so that the user can get a overall idea about maas region
>>>> controller.
>>>>
>>>> On 09-Aug-2017 1:09 AM, "Jeffrey Lane" <jeffrey.l...@canonical.com>
>>>> wrote:
>>>>
>>>> I think the question is something like "is there a directory on the
>>>> MAAS Server Filesystem (like /var/log/maas/) where I can find text
>>>> file logs for each node OUTSIDE maas.log and the web UI".
>>>>
>>>> I had a similar thought in that it would be nice at least if the UI
>>>> would allow me to download a note's deployment logs, rather than
>>>> forcing me to copy/paste several hundred lines of text to a file.  For
>>>> example, click on the "Deployment" tab and have a simple button at the
>>>> top of the output pane that says "Download Log" which would download
>>>> NODE_NAME-Deployment.log or whatever. It would also, for debugging
>>>> purposes, be nice to have those logs saved over time.  For example, if
>>>> I am deploying a node 10 times in a row to test changes to
>>>> curtin_userdata, or to test the effects of various firmware settings
>>>> on deployments, as i have been today.  It would be SUPER to be able to
>>>> go to a node specific directory, perhaps in /var/log/maas/, and be
>>>> able to see timestamped deployment logs for NODE_NAME so I can diff
>>>> them, or grep them all, or whatever I want en masse.
>>>>
>>>> On Tue, Aug 8, 2017 at 3:01 PM, Blake Rouse <blake.ro...@canonical.com>
>>>> wrote:
>>>> > I am some what confused on the question you are asking, but what I
>>>> believe
>>>> > you are asking about is "node-events". "node-events" is exposed over
>>>> the API
>>>> > which provides all events that have occurred on a node (machine or
>>>> device)
>>>> > since it has been added to MAAS.
>>>> >
>>>> > The same events can also be seen in the GUI on the machine details
>>>> page on
>>>> > the "Events" tab.
>>>> >
>>>> > On Tue, Aug 8, 2017 at 7:17 AM, sachidananda sahu <sachi...@gmail.com
>>>> >
>>>> > wrote:
>>>> >>
>>>> >> Hi All,
>>>> >>
>>>> >> In case any compute node failed in deployment then we are able to
>>>> see only
>>>> >> in maas GUI and maas logs, so is there place or file, where all
>>>> events,
>>>> >> statistics of different compute's data(failed in  enlisting,  failed
>>>> in
>>>> >> deployment, power states and all details) so that we can have
>>>> anoverall idea
>>>> >> about the all the compute nodes undergone different problems.
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Regards,
>>>> >> Sachidananda Sahu
>>>> >> +91-9035265767
>>>> >>
>>>> >> --
>>>> >> Maas-devel mailing list
>>>> >> Maas-devel@lists.ubuntu.com
>>>> >> Modify settings or unsubscribe at:
>>>> >> https://lists.ubuntu.com/mailman/listinfo/maas-devel
>>>> >>
>>>> >
>>>> >
>>>> > --
>>>> > Maas-devel mailing list
>>>> > Maas-devel@lists.ubuntu.com
>>>> > Modify settings or unsubscribe at:
>>>> > https://lists.ubuntu.com/mailman/listinfo/maas-devel
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> "Entropy isn't what it used to be."
>>>>
>>>> Jeff Lane -
>>>> Server Certification Lead, Warrior Poet, Biker, Lover of Pie
>>>> Phone: 919-442-8649
>>>> Ubuntu Ham: W4KDH                          Freenode IRC: bladernr or
>>>> bladernr_
>>>> gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417  C466 4ABD 3635 3A14 B2DD
>>>>
>>>>
>>>>
>>>> --
>>>> Maas-devel mailing list
>>>> Maas-devel@lists.ubuntu.com
>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>>> an/listinfo/maas-devel
>>>>
>>>>
>>>
>
-- 
Maas-devel mailing list
Maas-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/maas-devel

Reply via email to