[
https://issues.apache.org/jira/browse/CLOUDSTACK-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743627#comment-13743627
]
Ryan Lei commented on CLOUDSTACK-2906:
--------------------------------------
All such commands have been fixed in the 4.1.1 docs. This issue can be closed
now.
> Since Cloudstack 4.1.0 that many script commands, service names and
> directories have change the name from "cloud" to "cloudstack", which may
> cause confusing for the users who come from old versions.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2906
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2906
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.1.0
> Environment: CentOS 6.3 x86_64, cloudstack 4.1.0
> Reporter: wqmeng
> Priority: Minor
> Labels: Installation, documentation, guide
>
> Here is a list for those changes which mostly been used manually by the
> users. It would be better to add some notes in the Installation guide
> document to let the users know what have changed since cloudstack 4.1.0, it
> will help the users who like me to copy and paste commands from self custom
> script file. They will find everything not correct before they notice that
> "cloud-" have been changed to "cloudstack-".
> Thanks
> script commands:
> cloudstack-setup-databases
> cloudstack-setup-management
> cloudstack-setup-agent
> service names:
> cloudstack-management
> cloudstack-agent
> log files:
> /var/log/cloudstack/management/management-server.log
> /var/log/cloudstack/agent/agent.log
> /var/log/cloudstack/management/catalina.out
> properties files:
> /etc/cloudstack/agent/agent.properties
> /etc/cloudstack/management/db.properties
--
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
