David Nalley created CLOUDSTACK-344:
---------------------------------------
Summary: Docs still point to old location for many of the cloud-*
tools
Key: CLOUDSTACK-344
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-344
Project: CloudStack
Issue Type: Bug
Components: Doc
Reporter: David Nalley
Priority: Critical
Docs still point to /usr/lib64/cloud/agent/scripts
These have generally moved to /usr/lib64/cloud/common/scripts
A quick grep shows the following occurrences
./citrix-xenserver-installation.xml: <listitem><para>Copy the script
from the Management Server in
/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh
to the master host and ensure it is executable.</para></listitem>
./citrix-xenserver-installation.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py</para></entry>
./citrix-xenserver-installation.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/setupxenserver.sh</para></entry>
./citrix-xenserver-installation.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/make_migratable.sh</para></entry>
./citrix-xenserver-installation.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh</para></entry>
./host-add-xenserver-kvm-ovm.xml: <listitem><para>Copy the script
from the Management Server in
/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh
to the master host and ensure it is executable.</para></listitem>
./management-server-install-systemvm.xml: <programlisting>#
/usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m
/mnt/secondary -u
http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 -h
xenserver -s <optional-management-server-secret-key> -F</programlisting>
./management-server-install-systemvm.xml: <programlisting>#
/usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m
/mnt/secondary -u
http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova -h
vmware -s <optional-management-server-secret-key> -F</programlisting>
./management-server-install-systemvm.xml: <programlisting>#
/usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m
/mnt/secondary -u
http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h
kvm -s <optional-management-server-secret-key> -F</programlisting>
./prepare-system-vm-template.xml:
<programlisting>#
/usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m
/mnt/secondary -u
http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 -h
xenserver -s <optional-management-server-secret-key> -F</programlisting>
./prepare-system-vm-template.xml:
<programlisting>#
/usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m
/mnt/secondary -u
http://download.cloud.com/templates/acton/acton-systemvm-02062012.ova -h vmware
-s <optional-management-server-secret-key> -F</programlisting>
./prepare-system-vm-template.xml:
<programlisting>#
/usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m
/mnt/secondary -u
http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h
kvm -s <optional-management-server-secret-key> -F</programlisting>
./release-notes.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py</para></entry>
./release-notes.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/setupxenserver.sh</para></entry>
./release-notes.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/make_migratable.sh</para></entry>
./release-notes.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py</para></entry>
./release-notes.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/setupxenserver.sh</para></entry>
./release-notes.xml:
<entry><para>/usr/lib64/cloud/agent/scripts/vm/hypervisor/xenserver/make_migratable.sh</para></entry>
--
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