2. Section 3.1
Step 3&4 : it should be cloudstack-management and cloudstack-usage as the
naming conventions have been changed from 4.1 onwards.
Step 6 : The cloudstack 4.2 repo has not been published yet, currently at
http://cloudstack.apt-get.eu/ the repo is available only for 4.0.x and 4.1.x
What Indira pointed to, needs to be removed, step 6.g)
and 6.h) and step 8 also need to be removed
In step 6.f) It should be service cloudstack-agent stop
Step 9.b) : It should be sudo yum upgrade cloudstack-client
Step 9.c) : it should be sudo yum upgrade cloudstack-agent and the following line
is not required [[" During the installation of cloudstack-agent, the RPM will copy
your agent.properties,log4j-cloud.xml, and environment.properties from /etc/cloud/agent
to /etc/cloudstack/agent" ]]
Step 9.d.ii) : it should be sudo yum upgrade cloudstack-usage
3. Section 3.2
Step 1.e) : The URL of the vmware systemvm template is wrong. It should
be http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova .
The OSType should be [[Debian GNU/Linux 7.0
(32-bit) (or the highestDebian release number available in the dropdown)]]
Similarly, add templates for xenserver and kvm also.
Step 7 : Delete this step, it's not needed.
Step 16 : It should be cloudstack-sysvmadm
4. Section 3.3
Step 4.d) : For all the newly registered templates, make the OStype as
[[Debian GNU/Linux 7.0 (32-bit) (or the highest Debian release number available
in the dropdown)]]
Step 13.c) : It should be /etc/cloudstack/management/components.xml
Step 15.c) : It should be /etc/cloudstack/management/db.properties
Step 20 : Remove this step, it's not needed
Step 21.e) : It should be /etc/cloudstack/agent/agent.properties
Step 23.a) : It should be cloudstack-sysvmadm
5. In addition to all this, If we are using KVM hosts as rhel6.0/6.1 then
these extra steps need to be documented for each section, 3.2 and 3.3
(KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes one
or more
clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, you must first upgrade the
operating
system version on those hosts before upgrading CloudStack itself.
The first order of business will be to change the yum repository for each
system with
CloudStack packages. This means all management servers, and any hosts that have
the KVM
agent. (No changes should be necessary for hosts that are running VMware or
Xen.)
Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have
CloudStack packages installed.
[upgrade]
name=rhel63
baseurl=url-of-your-rhel6.3-repo
enabled=1
gpgcheck=0
[apache CloudStack]
name= Apache CloudStack
baseurl= http://cloudstack.apt-get.eu/rhel/4.0/
enabled=1
gpgcheck=0
If you are using the community provided package repository, change the baseurl
to http://
cloudstack.apt-get.eu/rhel/4.2/
If you're using your own package repository, change this line to read as
appropriate for your
4.2.0 repository.
b. Now that you have the repository configured
c. Upgrade the host operating system from RHEL 6.0 to 6.3:
yum upgrade
6. Also, in all the sections 3.2 and 3.3 , add this step for agent upgrades
After running this ,
Edit /etc/cloudstack/agent/agent.properties to change the resource parameter
from com.cloud.agent.resource.computing.LibvirtComputingResource to
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
We need to run the following too,
Upgrade all the existing bridge names to new bridge names by running this
script:
# cloudstack-agent-upgrade
. Install a libvirt hook with the following commands:
# mkdir /etc/libvirt/hooks
# cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu
# chmod +x /etc/libvirt/hooks/qemu
. Restart libvirtd.
# service libvirtd restart
. Start the agent.
# service cloudstack-agent start
Note : This step will be added after step 13.d in section 3.2 and 21.e in
section 3.3
7. We need to add a section for 4.0.x to 4.2 upgrades.
Thanks and regards,
Abhinav
-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Sunday, September 22, 2013 10:24 PM
To: dev@cloudstack.apache.org; Radhika Puthiyetath
Cc: us...@cloudstack.apache.org
Subject: RE: Volunteers to Complete the 4.2 Release Notes
Indra
I am unable to download the ReleaseNotes attachment from the bug at this time.
I will get back with more comments once I am able to get to it. Few comments
in-line
-----Original Message-----
From: Indra Pramana [mailto:in...@sg.or.id]
Sent: Friday, September 20, 2013 9:54 PM
To: Radhika Puthiyetath
Cc: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: Volunteers to Complete the 4.2 Release Notes
Hi Radhika,
I have downloaded the PDF document, thank you very much.
I noted that there is no specific upgrade instruction from 4.1.1 to
4.2.0.
What we have there is the generic upgrade instruction from 4.x.x to
4.2.0.
I have actually tried to follow this instruction on my earlier
(failed) upgrade attempt from 4.1.1 to 4.2.0, and found out that some
of the steps are no longer applicable. For example:
Step 6: Changes from /etc/cloud/management/components.xml to
/etc/cloudstack/management/componentContext.xml is no longer required
for upgrade from 4.1.1 to 4.2.0, since we are already using
/etc/cloudstack folder (instead of /etc/cloud folder) on 4.1.1.
[Animesh>] Yes this is left over and is not applicable for this upgrade and
will have to be cleaned up
Step 8h: Uninstalling old cloud-* packages are not required for
upgrade from 4.1.1 to 4.2.0 (cloud-* packages do not exist).
[Animesh>] Yes this is left over and is not applicable for this upgrade and
will have to be cleaned up
Step 10: (KVM Only): point a - Manually clean up /var/cache/cloudstack
<-- I believe this is supposed to be done on the KVM hosts? There is
no /var/cache/cloudstack folder on our KVM hosts running CloudStack
agent version 4.1.1. I have verified on all my KVM hosts. Is this step
required on the KVM hosts for upgrade from 4.1.1 to 4.2.0?
I found /var/cache/cloudstack folder on my CloudStack management
server though. Is this step supposed to be done on the management
server instead of the KVM hosts? If yes, it's not clearly mentioned.
Step 12: When I tried to run the cloudstack-sysvmadm script to restart
the system VMs, the script failed to run with some error messages.
Unfortunately, I didn't manage to take down the error messages. Is
this step required for upgrade from 4.1.1 to 4.2.0? If for some
reason, we are not able to run the script, are we able to restart the
system VMs manually (say from the CloudStack GUI)?
Looking forward to your reply, thank you.
Cheers.
On Fri, Sep 20, 2013 at 5:45 PM, Radhika Puthiyetath <
radhika.puthiyet...@citrix.com> wrote:
Thanks Indra.****
** **
I shall attach the PDF file at
https://issues.apache.org/jira/browse/CLOUDSTACK-4245.****
** **
** **
** **
*From:* Indra Pramana [mailto:in...@sg.or.id]
*Sent:* Friday, September 20, 2013 12:07 PM
*To:* Radhika Puthiyetath
*Cc:* us...@cloudstack.apache.org
*Subject:* Re: Volunteers to Complete the 4.2 Release Notes****
** **
Hi Radhika,****
** **
May I know how can I view the release notes in normal HTML format,
instead of the original XML format?****
** **
Does it specifically contain migration steps from 4.1.1 to
4.2.0?****
** **
Would like to try again to upgrade my current CloudStack 4.1.1 to
4.2.0, provided I can get the detailed instruction on what to do.
Last time I tried to follow the existing documentation on the
.tar.bz2 file (provided by Animesh when he started the vote) and
some of the steps seem to be not applicable anymore, and I might
have missed out some other steps which are actually required.****
** **
Looking forward to your reply, thank you.****
** **
Cheers.****
** **
** **
On Thu, Sep 19, 2013 at 2:42 PM, Radhika Puthiyetath <
radhika.puthiyet...@citrix.com> wrote:****
This has been updated. Could someone please validate the API section
?****
-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]****
Sent: Sunday, September 15, 2013 4:16 AM
To: <us...@cloudstack.apache.org>
Cc: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: Volunteers to Complete the 4.2 Release Notes
I have added a public filters for known issues and fixed issues that
we can put in release notes. This way the data is dynamic and up to
date
Thanks
Animesh
On Sep 13, 2013, at 8:53 AM, "Radhika Puthiyetath" <
radhika.puthiyet...@citrix.com> wrote:
Who is volunteering to provide the list of Fixed issues for the RN?
-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Wednesday, August 28, 2013 4:40 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: RE: Volunteers to Complete the 4.2 Release Notes
Community help is needed to fix up the release notes, any
volunteers
Animesh
-----Original Message-----
From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
Sent: Tuesday, August 13, 2013 1:01 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Volunteers to Complete the 4.2 Release Notes
Hi,
Looking for volunteers to help me with the 4.2 Release Notes.
I have started filling in the new feature section, and checked in
to the
4.2 branch.
A defect is filed
https://issues.apache.org/jira/browse/CLOUDSTACK-4245
.
Thanks for the help
-Radhika****
** **
