You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Santhosh Kumar Edukulla (JIRA)" <ji...@apache.org> on 2014/01/27 19:21:37 UTC

[jira] [Created] (CLOUDSTACK-5957) [Automation]: Collect management Server and other relevant logs and provide facility for analysis

Santhosh Kumar Edukulla created CLOUDSTACK-5957:
---------------------------------------------------

             Summary: [Automation]: Collect management Server and other relevant logs and provide facility for analysis
                 Key: CLOUDSTACK-5957
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5957
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Automation, marvin
            Reporter: Santhosh Kumar Edukulla
            Assignee: Santhosh Kumar Edukulla


1. Provide a facility where for a given regression or bvt run,where we should have logs collected and stored at a given place.
2. The logs include the following :
 Management server logs, test logs( run,results etc )
3. The process should be automated. 

Phase1: 
1. Collect and store the logs at a given location post  every regression\BVTrun.
2.  We will  add a new job to CI facility and this job will be added as downstream project for every regression or bvt run post the run.
3. The job takes few configurable parameters viz., management server, path for logs,remote location,path etc.
4. Using the configuration, the script copies the files to the relevant location.
5. Initially, a vm with few specific setup will be used to store the logs. 
6. The logs will  be remotely copied in a compressed format, by specific build and commit id.
7. The remote copied folder ( compressed ) post the copy, will have test_logs, cs_logs etc along with metadata like last commit-id, build information,cs version information and any other data required.
8. The folder name can be used along with metadata to identify the relevant logs.

Phase2:
1. provide few interfaces( through web ) to analyze and extract this information to user.
2. Provide a UI if possible for easy reconciliation of logs.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)