You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cloudstack.apache.org by "Nik Martin (JIRA)" <ji...@apache.org> on 2013/02/26 16:38:13 UTC

[jira] [Updated] (CLOUDSTACK-1409) Cloudstack Admin guide additions

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nik Martin updated CLOUDSTACK-1409:
-----------------------------------

    Description: The cloudstack admin guide has little to no documentation for troubleshooting and maintenance of cloudstack: log files, how to replace a host, how to replace a controller, etc.  We are going through the different failure scenarios in a production cloud, and the very first one, a management controller failure/replacement, is not documented anywhere.  (was: The cloudstack admin guide has little to no documentation for troubleshooting and maintenance of cloudtsack - log files, how to replace a host, how to replace a controller, etc.  We are going through the different failure scenarios in a production cloud, and the very first one, a management controller failure/replacement, is not documented anywhere.)
    
> Cloudstack Admin guide additions
> --------------------------------
>
>                 Key: CLOUDSTACK-1409
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1409
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.0.1
>            Reporter: Nik Martin
>              Labels: documentation
>
> The cloudstack admin guide has little to no documentation for troubleshooting and maintenance of cloudstack: log files, how to replace a host, how to replace a controller, etc.  We are going through the different failure scenarios in a production cloud, and the very first one, a management controller failure/replacement, is not documented anywhere.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira