[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Lei updated CLOUDSTACK-3180:
---------------------------------

    Summary: [DOC] Path /usr/lib64/cloud/common/ for CentOS should be changed 
to /usr/share/cloudstack-common  (was: [DOC] path /usr/lib64/cloud/common/ for 
CentOS should be changed to /usr/share/cloudstack-common)
    
> [DOC] Path /usr/lib64/cloud/common/ for CentOS should be changed to 
> /usr/share/cloudstack-common
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3180
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3180
>             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 still many instructions that use the old path for scripts.
> All the /usr/lib64/cloud/common should now be changed to 
> /usr/share/cloudstack-common for CentOS.
> 7.6.1.1.1. XenServer Host Additional Requirements 
> (host-add-xenserver-kvm-ovm.xml) &
> 8.2.10.4.6. Complete the Bonding Setup Across the Cluster 
> (citrix-xenserver-installation.xml)
> Copy the script from the Management Server in 
> /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh
>  to the master host and ensure it is executable.
> 8.2.11. Upgrading XenServer Versions (citrix-xenserver-installation.xml)
> Copy this Management Server file...
> /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py
> /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/setupxenserver.sh
> /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/make_migratable.sh
> /usr/lib64/cloud/common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh

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