cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavan Kumar Bandarupally (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4570) service cloud-management wrongly named
Date Fri, 30 Aug 2013 11:19:51 GMT

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

Pavan Kumar Bandarupally updated CLOUDSTACK-4570:
-------------------------------------------------

    Priority: Critical  (was: Major)
    
> service cloud-management wrongly named
> --------------------------------------
>
>                 Key: CLOUDSTACK-4570
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4570
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.2.0
>            Reporter: Pavan Kumar Bandarupally
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> 4.2.6 LDAP User Authentication: Limitation
> "service cloud-management restart"  should be changed to "service cloudstack-management
restart"
> Apart from that there is a minor spelling mistake in section "3.7. About Secondary Storage"
> In the last but one paragraph in that section , swift is misspelled as swoft.
> The NFS storage in each zone acts as a staging area
> through which all templates and other secondary storage data pass before being forwarded
to Swoft
> or S3

--
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

Mime
View raw message