Apache CloudStack 4.3.0 Released

Apache CloudStack 4.3.0 is out with an enhanced UI and new color theme!!!

Screen Shot 2014-04-20 at 12.09.47 amScreen Shot 2014-04-20 at 12.10.06 am

For those upgrading from 4.2.1 to 4.3.0, the official upgrade instructions are at http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/rnotes.html#upgrade-from-4-2-x-to-4-3.

Some additional notes for upgrading while upgrading from 4.2.1 to 4.3 in a CentOS6 environment:

  1. The upgrade instructions require a yum upgrade cloudstack-management which pulls in newer versions of cloudstack-common, cloudstack-awsapi and cloudstack-management. Ensure you also run yum upgrade cloudstack-usage cloudstack-cli to pull in newer versions of these packages
  2. After the upgrade, the browser cache had to be cleared before the new UI theme started rendering correctly
  3. Console access stopped working after the upgrade. This was fixed by setting consoleproxy.url.domain to empty and secstorage.encrypt.copy to false followed by a SSVM and CPVM stop/start cycle and a management-server restart. See this mailing list discussion

A complete list of new features is available at http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/about.html

Shanker Balan

Shanker Balan is a devops and infrastructure freelancer with over 14 years of industry experience in large scale Internet systems. He is available for both short term and long term projects on contract. Please use the Contact Form for any enquiry.

More Posts - Website

Follow Me:
TwitterLinkedIn

Published by

Shanker Balan

Shanker Balan is a devops and infrastructure freelancer with over 14 years of industry experience in large scale Internet systems. He is available for both short term and long term projects on contract. Please use the Contact Form for any enquiry.

2 thoughts on “Apache CloudStack 4.3.0 Released”

  1. Setting consoleproxy.url.domain to empty causes some MAC OSX variants to have NOT working Console Proxy URL. Correct way is to set consoleproxy.url.domain to realhostip.com instead of the default one *.realhostip.com.
    Console works fine after that.
    Cheers

Leave a Reply