You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Daniel Foster (JIRA)" <ji...@apache.org> on 2012/11/08 17:30:13 UTC

[jira] [Commented] (CLOUDSTACK-462) A few corrections to make to the 4.0.0 installation guide

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

Daniel Foster commented on CLOUDSTACK-462:
------------------------------------------

Further, with the management server setup, before you can proceed to section 5 and log in, you must run cloud-setup-management.  Thanks to skeelime in IRC for the heads up on that one.
                
> A few corrections to make to the 4.0.0 installation guide
> ---------------------------------------------------------
>
>                 Key: CLOUDSTACK-462
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-462
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Doc
>    Affects Versions: 4.0.0
>         Environment: CentOS 6
>            Reporter: Daniel Foster
>            Priority: Minor
>
> I've followed the 4.0.0 installation guide and there are a few things that don't work as written:
> 4.4.2 There is no .repo file at the link, so I created a simple one and chose to ignore GPG checking.  It is as follows:
> # cat /etc/yum.repos.d/cloudstack.repo
> [cloudstack]
> name=cloudstack
> baseurl=http://cloudstack.apt-get.eu/rhel/4.0/
> enabled=1
> gpgcheck=0
> 4.5.3.1 Directory for vhd-util only exists after yum install cloud-client, and following yum-install cloud-client, is already present in /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver
> 4.5.4.1 step 5, cloud-setup-databases complains about selinux, it needs to be put in permissive mode before this.  I followed the steps intended for the hosts in section 8.1.6
> 4.5.5.2 setting up management server, but starts talking about the hypervisor host - not set up yet!

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