[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705420#comment-13705420
 ] 

ASF subversion and git services commented on CLOUDSTACK-3179:
-------------------------------------------------------------

Commit 63206d601af9afc0f1001eb23e14ff75e0db62b9 in branch refs/heads/master 
from [~gavinlee]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=63206d6 ]

[DOC]Change cloud- to cloudstack- for the service and fix script path issue
CLOUDSTACK-3179,CLOUDSTACK-3180

Conflicts:

        docs/en-US/Release_Notes.xml
        docs/en-US/citrix-xenserver-installation.xml

                
> [DOC] Service cloud-management should be changed to service 
> cloudstack-management
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3179
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3179
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc
>    Affects Versions: 4.1.0, 4.2.0, Future
>         Environment: platform-independent
>            Reporter: Ryan Lei
>            Assignee: gavin lee
>            Priority: Critical
>             Fix For: 4.1.1, 4.2.0, Future
>
>
> A quick search through the current documentation and git 4.1, I found this 
> one remaining cloud-management bug in the Installation Guide:
> 8.2.11. Upgrading XenServer Versions (citrix-xenserver-installation.xml)
> c. Restart the Management Server and Usage Server. You only need to do this 
> once for all clusters.
> # service cloud-management start
> # service cloudstack-usage start
> The first command still uses the old service name. It should be changed to
> # service cloudstack-management start

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

Reply via email to