Realhostip service extended till Sep 30th
Folks I wanted to provide an update on shutting down of RealhostIp service. Citrix has decided to move the date by one quarter and the new date will be Sep 30th. The new dates allow users of CloudStack additional time for updating their infrastructure. While testing Realhostip fixes additional product issues were found which are tracked in following three defects CLOUDSTACK-6499 [1], CLOUDSTACK-6599 [2], CLOUDSTACK-6824 [3] . These defects are fixed in 4.4 and master branch. Please verify in your setups. If you are on older version of CloudStack do plan on upgrading to 4.4 . Additional details on fixes are available in JIRA. Updated wiki with steps will be published shortly. [1] https://issues.apache.org/jira/browse/CLOUDSTACK-6499 [2] https://issues.apache.org/jira/browse/CLOUDSTACK-6599 [3] https://issues.apache.org/jira/browse/CLOUDSTACK-6824 Thanks Animesh > -Original Message- > From: John Kinsella [mailto:j...@stratosec.co] > Sent: Thursday, April 17, 2014 8:35 AM > To: ; users...@cloudstack.apache.org; > > Subject: REMINDER RealhostIP going away > > Reminder, folks - please migrate off RealhostIP.com or you're going to get a > nasty surprise this summer. More info at link below. > > https://blogs.apache.org/cloudstack/entry/RealhostIP_service_is_being_ret > ired
RE: [SCREENCAST] 4.0.2 testing procedure
Sebastian it is really good, can you update Release test procedure wiki with link to your video. > -Original Message- > From: Sebastien Goasguen [mailto:run...@gmail.com] > Sent: Friday, April 19, 2013 8:53 AM > To: d...@cloudstack.apache.org > Subject: [SCREENCAST] 4.0.2 testing procedure > > Hi, > > I just uploaded an HD screencast that shows me testing the 4.0.2 release: > http://www.youtube.com/watch?v=vvgIkF1e1QE&list=PLb899uhkHRoZCRE0 > 0h_9CRgUSiHEgFDbC&index=1 > > Check it out and do it yourself, then vote !!! > > -Sebastien
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: d...@cloudstack.apache.org; users@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
[VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth round)
The vote has *passed* with the following results (binding PMC votes indicated with a "*" next to their name: +1 : Edison*, Chiradeep*, Sebastien*, Prasanna*, Rajesh Batala, Ove Ewerlid -1 : Marcus*, Chip*, Simon Weller I'm going to proceed with moving the release into the distribution repo now and work on release notes and other documentation tasks The -1 are recorded for the CLVM issue [1]. A fix for this issue is available and fixed in 4.2-forward branch and will be available for 4.2.1. If anyone needs the fix now they can cherry-pick from 4.2-forward with commitId f2c5b5fbfe45196dfad2821fca513ddd6efa25c9. This issue will be release noted. [1] https://issues.apache.org/jira/browse/CLOUDSTACK-4618 Thanks Animesh
RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth round)
Ron I am not too happy with the documentation side too and will put in time in next 2-3 days to clear up whatever I can on documentation before the formal annoucement. This is a community effort and every help is appreciated. Animesh > -Original Message- > From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > Sent: Tuesday, September 10, 2013 3:56 PM > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth round) > > I am very disappointed that 4.2 will be released without fixing > longstanding documentation problems. > There is no point is asking us to file JIRA issues if the developers are > not going to fix them. > > The first impression for CloudStack is made in the installation docs. It is > makes the whole project look amateurish when the installation does not > work. > > > Ron > > On 10/09/2013 4:12 PM, Animesh Chaturvedi wrote: > > > > The vote has *passed* with the following results (binding PMC votes > indicated with a "*" next to their name: > > > > +1 : Edison*, Chiradeep*, Sebastien*, Prasanna*, Rajesh Batala, Ove > > +Ewerlid > > -1 : Marcus*, Chip*, Simon Weller > > > > I'm going to proceed with moving the release into the distribution > > repo now and work on release notes and other documentation tasks > > > > The -1 are recorded for the CLVM issue [1]. A fix for this issue is > available and fixed in 4.2-forward branch and will be available for 4.2.1. > If anyone needs the fix now they can cherry-pick from 4.2-forward with > commitId f2c5b5fbfe45196dfad2821fca513ddd6efa25c9. This issue will be > release noted. > > > > > > [1] https://issues.apache.org/jira/browse/CLOUDSTACK-4618 > > > > > > Thanks > > Animesh > > > > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102
RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth round)
Thanks Ron I am planning to work on Release Notes in the morning, do you have time later in the day or tomorrow morning PST for Installation issues. Thanks Animesh > -Original Message- > From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > Sent: Wednesday, September 11, 2013 5:32 AM > To: Animesh Chaturvedi > Cc: users@cloudstack.apache.org; d...@cloudstack.apache.org > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth > round) > > I would be happy to work with you on the issues that I raised and on > the installation process in general. > I can set up a collaboration meeting if that suits you. > > Ron > > > On 10/09/2013 7:46 PM, Animesh Chaturvedi wrote: > > Ron > > > > I am not too happy with the documentation side too and will put in > time in next 2-3 days to clear up whatever I can on documentation > before the formal annoucement. This is a community effort and every > help is appreciated. > > > > > > Animesh > > > >> -Original Message- > >> From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > >> Sent: Tuesday, September 10, 2013 3:56 PM > >> To: users@cloudstack.apache.org; d...@cloudstack.apache.org > >> Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth > >> round) > >> > >> I am very disappointed that 4.2 will be released without fixing > >> longstanding documentation problems. > >> There is no point is asking us to file JIRA issues if the developers > >> are not going to fix them. > >> > >> The first impression for CloudStack is made in the installation > docs. > >> It is makes the whole project look amateurish when the installation > >> does not work. > >> > >> > >> Ron > >> > >> On 10/09/2013 4:12 PM, Animesh Chaturvedi wrote: > >>> The vote has *passed* with the following results (binding PMC votes > >> indicated with a "*" next to their name: > >>> +1 : Edison*, Chiradeep*, Sebastien*, Prasanna*, Rajesh Batala, Ove > >>> +Ewerlid > >>> -1 : Marcus*, Chip*, Simon Weller > >>> > >>> I'm going to proceed with moving the release into the distribution > >>> repo now and work on release notes and other documentation tasks > >>> > >>> The -1 are recorded for the CLVM issue [1]. A fix for this issue is > >> available and fixed in 4.2-forward branch and will be available for > 4.2.1. > >> If anyone needs the fix now they can cherry-pick from 4.2-forward > >> with commitId f2c5b5fbfe45196dfad2821fca513ddd6efa25c9. This issue > >> will be release noted. > >>> > >>> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-4618 > >>> > >>> > >>> Thanks > >>> Animesh > >>> > >> > >> -- > >> Ron Wheeler > >> President > >> Artifact Software Inc > >> email: rwhee...@artifact-software.com > >> skype: ronaldmwheeler > >> phone: 866-970-2435, ext 102 > > > > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102
RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth round)
I have set up a GTM with Ron tomorrow 10 AM PST. Anyone else interested is welcome to join, GTM details are provided below 1. Please join my meeting. https://www1.gotomeeting.com/join/725491376 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United States: +1 (224) 649-0001 United States (toll-free): 1 877 309 2073 Access Code: 725-491-376 Audio PIN: Shown after joining the meeting Meeting ID: 725-491-376 GoToMeeting(r) Online Meetings Made Easy(r) Not at your computer? Click the link to join this meeting from your iPhone(r), iPad(r) or Android(r) device via the GoToMeeting app. Thanks Animesh > -Original Message- > From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > Sent: Wednesday, September 11, 2013 5:32 AM > To: Animesh Chaturvedi > Cc: users@cloudstack.apache.org; d...@cloudstack.apache.org > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth > round) > > I would be happy to work with you on the issues that I raised and on the > installation process in general. > I can set up a collaboration meeting if that suits you. > > Ron > > > On 10/09/2013 7:46 PM, Animesh Chaturvedi wrote: > > Ron > > > > I am not too happy with the documentation side too and will put in > time in next 2-3 days to clear up whatever I can on documentation before > the formal annoucement. This is a community effort and every help is > appreciated. > > > > > > Animesh > > > >> -Original Message- > >> From: Ron Wheeler [mailto:rwhee...@artifact-software.com] > >> Sent: Tuesday, September 10, 2013 3:56 PM > >> To: users@cloudstack.apache.org; d...@cloudstack.apache.org > >> Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fourth > >> round) > >> > >> I am very disappointed that 4.2 will be released without fixing > >> longstanding documentation problems. > >> There is no point is asking us to file JIRA issues if the developers > >> are not going to fix them. > >> > >> The first impression for CloudStack is made in the installation docs. > >> It is makes the whole project look amateurish when the installation > >> does not work. > >> > >> > >> Ron > >> > >> On 10/09/2013 4:12 PM, Animesh Chaturvedi wrote: > >>> The vote has *passed* with the following results (binding PMC votes > >> indicated with a "*" next to their name: > >>> +1 : Edison*, Chiradeep*, Sebastien*, Prasanna*, Rajesh Batala, Ove > >>> +Ewerlid > >>> -1 : Marcus*, Chip*, Simon Weller > >>> > >>> I'm going to proceed with moving the release into the distribution > >>> repo now and work on release notes and other documentation tasks > >>> > >>> The -1 are recorded for the CLVM issue [1]. A fix for this issue is > >> available and fixed in 4.2-forward branch and will be available for > 4.2.1. > >> If anyone needs the fix now they can cherry-pick from 4.2-forward > >> with commitId f2c5b5fbfe45196dfad2821fca513ddd6efa25c9. This issue > >> will be release noted. > >>> > >>> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-4618 > >>> > >>> > >>> Thanks > >>> Animesh > >>> > >> > >> -- > >> Ron Wheeler > >> President > >> Artifact Software Inc > >> email: rwhee...@artifact-software.com > >> skype: ronaldmwheeler > >> phone: 866-970-2435, ext 102 > > > > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102
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" 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: d...@cloudstack.apache.org; users@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: d...@cloudstack.apache.org; users@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
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: users@cloudstack.apache.org; d...@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:* users@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: > > Cc: d...@cloudstack.apache.org; users@cloudstack.apache.org > > Subject: Re: Volunteers to Complete the 4.2 Release Notes > > > > I have added a pu
RE: Upgrade from 4.1.1 to 4.2.0 failed: Error creating bean with name 'apiDBUtils'
Can you post the log, mailing list will not take an attachment, so you can create a JIRA ticket and put in the log as attachment. Thanks Animesh > -Original Message- > From: Indra Pramana [mailto:in...@sg.or.id] > Sent: Monday, September 23, 2013 10:10 AM > To: users@cloudstack.apache.org; d...@cloudstack.apache.org > Subject: Upgrade from 4.1.1 to 4.2.0 failed: Error creating bean with > name 'apiDBUtils' > > Dear all, > > Apologise, reposting this issue since the subject on the earlier thread > might not be clearly depicting the problem. > > I tried to perform upgrade of CloudStack version 4.1.1 to 4.2.0, and I > am not able to access the CloudStack GUI after the upgrade. > > I am able to start the cloudstack-management service: > > root@cs-mgmt-01:/usr/share# service cloudstack-management start > * Starting CloudStack-specific Tomcat servlet engine cloudstack- > management [ OK ] > > However, I am not able to access the GUI with this error message: > > = > HTTP Status 404 - > > type Status report > > message > > description The requested resource () is not available. > Apache Tomcat/6.0.35 > = > > I am getting this error message on > /var/log/cloudstack/management/management-server.log: > > = > 2013-09-23 21:36:57,003 ERROR [web.context.ContextLoader] (main:null) > Context initialization failed > org.springframework.beans.factory.BeanCreationException: Error creating > bean with name 'apiDBUtils': Injection of autowired dependencies failed; > = > > Full log can be found here: http://pastebin.com/0FP9itAf > > Any help is greatly appreciated, thank you.
RE: Volunteers to Complete the 4.2 Release Notes
; 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: d...@cloudstack.apache.org; Radhika Puthiyetath > Cc: users@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: users@cloudstack.apache.org; d...@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:* users@cloudstack.apache.org > > > > > > *Subject:* Re: Volunteers to Complete the
CloudSatck SF BayArea Meetup on October 15th @ SAP Labs : Spread the word
Folks I am happy to announce the CloudStack Bay area meetup is on October 15th. Here is the link for meetup details http://www.meetup.com/CloudStack-SF-Bay-Area-Users-Group/events/141814852/ If you wish to be the speaker for this meetup please reach out to Karen Vuong, John Kinsella or Animesh. Please spread the word. Thanks Animesh Folks
RE: Volunteers to Complete the 4.2 Release Notes
nd 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: d...@cloudstack.apache.org; Radhika Puthiyetath > >> Cc: users@
RE: Unable to create instance after upgrading to CloudStack 4.2.0
Copying Sanjay Animesh > -Original Message- > From: Indra Pramana [mailto:in...@sg.or.id] > Sent: Tuesday, October 01, 2013 11:06 AM > To: d...@cloudstack.apache.org; users@cloudstack.apache.org > Subject: Re: Unable to create instance after upgrading to CloudStack > 4.2.0 > > Dear all, > > Further investigation reveals that there might be some issues with the > schema upgrade. When we check the resource_count table for the account > ID: > > mysql> select * from resource_count where account_id=2; > +++---+---+---+ > | id | account_id | domain_id | type | count | > +++---+---+---+ > | 17 | 2 | NULL | user_vm |30 | > | 18 | 2 | NULL | public_ip | 4 | > | 19 | 2 | NULL | volume|40 | > | 20 | 2 | NULL | snapshot | 1 | > | 21 | 2 | NULL | template |40 | > | 22 | 2 | NULL | project | 0 | > | 23 | 2 | NULL | network | 2 | > | 24 | 2 | NULL | vpc | 0 | > +++---+---+---+ > > There's no 'primary_storage' type there. In comparison, Abhinav's > database contains the details: > > mysql> SELECT * FROM cloud.resource_count where account_id=2; > +++---+---+-+ > | id | account_id | domain_id | type | count | > +++---+---+-+ > | 17 | 2 | NULL | user_vm | 4 | > | 18 | 2 | NULL | public_ip | 1 | > | 19 | 2 | NULL | volume| 3 | > | 20 | 2 | NULL | snapshot | 3 | > | 21 | 2 | NULL | template | 1 | > | 22 | 2 | NULL | project | 0 | > | 23 | 2 | NULL | network | 2 | > | 24 | 2 | NULL | vpc | 1 | > | 33 | 2 | NULL | cpu | 2 | > | 34 | 2 | NULL | memory|1536 | > | 35 | 2 | NULL | primary_storage | 8589934592 | > | 36 | 2 | NULL | secondary_storage | 27866955776 | > +++---+---+-+ > > These types are missing from my resource_count table for each of the > accounts: > > | 33 | 2 | NULL | cpu | 2 | > | 34 | 2 | NULL | memory|1536 | > | 35 | 2 | NULL | primary_storage | 8589934592 | > | 36 | 2 | NULL | secondary_storage | 27866955776 | > > I tried to re-do the schema upgrade manually pertaining to that > particular table, which is part of this section under: > > /usr/share/cloudstack-management/setup/db/schema-410to420.sql > > DROP VIEW IF EXISTS `cloud`.`account_view`; CREATE VIEW > `cloud`.`account_view` AS > > But I am still not able to get the four types (cpu, memory, > primary_storage, secondary_storage) to appear on my resource_count > table. > > Anyone can help? This is my third attempt to upgrade to 4.2.0 and I > don't want to revert back again now. > > Looking forward to your reply, thank you. > > Cheers. > > > > On Wed, Oct 2, 2013 at 12:49 AM, Indra Pramana wrote: > > > Dear all, > > > > I am having problems of unable to create new instances after upgrading > > to 4.2.0. The error message is: > > > > Failed to increment resource count of type primary_storage for account > > id=2 > > > > Excerpt from management-server.log: > > > > > > 2013-10-02 00:40:57,770 DEBUG [cloud.api.ApiServlet] > > (catalina-exec-15:null) ===START=== -- GET > > command=queryAsyncJobResult&jobId=183063da-fb08-425b-8057-157e33320674 > > &response=json&sessionkey=VEyky3f1rsQVfLVs9pGg2sXh60o%3D&_=13806456467 > > 39 > > 2013-10-02 00:40:57,785 DEBUG [cloud.api.ApiDispatcher] > > (catalina-exec-16:null) InfrastructureEntity name > > is:com.cloud.offering.ServiceOffering > > 2013-10-02 00:40:57,791 DEBUG [cloud.api.ApiDispatcher] > > (catalina-exec-16:null) ControlledEntity name > > is:com.cloud.template.VirtualMachineTemplate > > 2013-10-02 00:40:57,795 DEBUG [cloud.api.ApiDispatcher] > > (catalina-exec-16:null) ControlledEntity name > > is:com.cloud.network.Network > > 2013-10-02 00:40:57,798 DEBUG [cloud.api.ApiDispatcher] > > (catalina-exec-16:null) InfrastructureEntity name > > is:com.cloud.offering.DiskOffering > > 2013-10-02 00:40:57,813 DEBUG [cloud.network.NetworkModelImpl] > > (catalina-exec-16:null) Service SecurityGroup is not supported in the > > network id=238 > > 2013-10-02 00:40:57,828 DEBUG [cloud.api.ApiServlet] > > (catalina-exec-15:null) ===END=== -- GET > > command=queryAsyncJobResult&jobId=183063da-fb08-425b-8057-157e33320674 > > &response=json&sessionkey=VEyky3f1rsQVfLVs9pGg2sXh60o%3D&_=13
RE: CloudStack Bay Area Meetup
Adding the users mailing list too > -Original Message- > From: Amogh Vasekar [mailto:amogh.vase...@citrix.com] > Sent: Monday, October 14, 2013 11:08 AM > To: d...@cloudstack.apache.org > Subject: CloudStack Bay Area Meetup > > Hi All, > > The CloudStack Bay Area meet-up will be held tomm. (10/15) with Juniper > doing a Contrail integration demo, followed by a DevCloud intro session > to help new CloudStack developers. > More details on > http://www.meetup.com/CloudStack-SF-Bay-Area-Users- > Group/events/141814852/ > > Do join in if around! > > Thanks, > Amogh
RE: 4.2.1 anytime soon?
-Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Wednesday, November 27, 2013 6:24 PM To: users@cloudstack.apache.org Subject: Re: 4.2.1 anytime soon? On 27.11.2013 18:10, sebgoa wrote: > My advice would be to wait couple days for the official 4.2.1 but if > you are eager you can grab those rpms and start ironing out your > upgrade procedure (from where you are at to ~4.2.1) on your dev > systems. Is there a list somewhere with features and bugfixes that will make it into 4.2.1? Lucian Animesh> Here is the list of issues that are fixed https://issues.apache.org/jira/issues/?filter=12325707. This being a maintenance release there are no new features -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
