Joe Brockmeier created CLOUDSTACK-3138:
------------------------------------------
Summary: Flaws in upgrade documentation from 3.0.2 -> 4.1.0
Key: CLOUDSTACK-3138
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3138
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Doc
Affects Versions: 4.1.0
Reporter: Joe Brockmeier
Priority: Critical
Fix For: 4.1.1
Reported on the mailing list (http://markmail.org/message/ussthbb6sx6kjm2j)
there are many errors in release notes for upgrade form CS 3.0.2 to 4.0.1.
Here are just a few, from the top of my head. I suggest you correct them.
1. Location of config files is not at /etc/cloud/ but rather at
/etc/cloudstack now.
2. components.xml is nowhere to be found in /etc/cloudstack
3. server.xml generation failed, because i had enabled ssl in it. It
required me to generate them from scratch.
4. There were no instructions for enabling https, anywhere. I had to fix
server.xml and tomcat6.xml to use my certificate.
5. cloud-sysvmadm is nonexistent. I think there is cloudstack-sys.. Also
switches are wrong.
6. Python and bash scripts are now located
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/ instead
of /usr/lib64/cloud/common/ scripts/vm/hypervisor/
xenserver/xenserver60/ as documentation would tell you.
7. for pbd in `xe pbd-list currently-attached=false| grep ^uuid | awk
'{print $NF}'`; do xe pbd-plug uuid=$pbd ; doesn't work:
[root@x1 ~]# for pbd in `xe pbd-list currently-attached=false| grep
^uuid | awk '{print $NF}'`; do xe pbd-plug uuid=$pbd
>
...
--
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