incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "edison su (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-376) Issues in docs
Date Thu, 18 Oct 2012 23:38:03 GMT

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

edison su commented on CLOUDSTACK-376:
--------------------------------------

I read the docs build from jenkins.c.o on 4.0 branch, issues I find:

1. "Provde the CPU, memory, storage" in page 7, Provde should be "Provide"
2. "Also supported: CentOS/RHEL 5.5 or Ubuntu 10.04" in page 14, we don't test 4.0 on this
OS, there is no specific build for these OS also, so better to remove them from the docs.
3. "• Statically allocated IP Address" can be removed, but with a notice, if dhcp is used
for hosts, make sure there is no conflict between dhcp server used for these hosts and the
dhcp router created by cloudstack.
4. "/usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt " in page 27:
the path should be "/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt
"
5. add download vhd-util in page 26
6. from "Install and Configure libvirt" page 58 to "7.1.6.2. Open ports in Ubuntu" in page
64, I think we don't need to manually configure libvirt and selinux in 4.0 for kvm, as cloud-setup-agent
will do all the same thing for you automatically when adding the host from UI.
                
> Issues in docs
> --------------
>
>                 Key: CLOUDSTACK-376
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-376
>             Project: CloudStack
>          Issue Type: Bug
>            Reporter: edison su
>            Assignee: Jessica Tomechak
>            Priority: Critical
>
> 19:03 < edison_cs> • Provde the CPU
> 19:03 < edison_cs> in page 7
> 19:03 < edison_cs> 4.0 installation guide

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