cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Lei (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-3182) [DOC] Path /etc/cloud should be changed to /etc/cloudstack
Date Tue, 25 Jun 2013 06:35:19 GMT
Ryan Lei created CLOUDSTACK-3182:
------------------------------------

             Summary: [DOC] Path /etc/cloud should be changed to /etc/cloudstack
                 Key: CLOUDSTACK-3182
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3182
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Doc
    Affects Versions: 4.1.0
         Environment: platform-independent
            Reporter: Ryan Lei
             Fix For: 4.1.1


There are several paths still saying /etc/cloud/xxx. These should now be changed to /etc/cloudstack/xxx.

[Installation Guide]

9.3.1. Failover (database-replication.xml)
4. Make a change so that the Management Server uses the new database. The simplest process
here is to put the IP address of the new database server into each Management Server's /etc/cloud/management/db.properties.

11.3.3. Modifying the AWS API Port (aws-ec2-configuration.xml)
a. Edit the files /etc/cloud/management/server.xml, /etc/cloud/management/server-nonssl.xml,
and /etc/cloud/management/server-ssl.xml.

[Admin Guide]

18.2. Changing the Database Configuration (change-database-config.xml)
The CloudStack Management Server stores database configuration information (e.g., hostname,
port, credentials) in the file /etc/cloud/management/db.properties.

18.3. Changing the Database Password (change-database-password.xml)
I found 5 such matches. Not to list here.

21.2. Increase Management Server Maximum Memory (increase-management-server-max-memory.xml)
1. Edit the Tomcat configuration file:
/etc/cloud/management/tomcat6.conf



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