Hello, 4.7.1 (and 4.8.0) are basically out, you can find the packages at http://cloudstack.apt-get.eu/ - the release notes and official announcement seem to be delayed a bit. You can use the 4.6 systemvm with both of the releases.
Re Ubuntu I am sorry, no idea, I use CentOS 6 & 7.. You should be able to build the packages yourself though from source though, try it out. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Indra Pramana" <[email protected]> > To: [email protected] > Sent: Tuesday, 9 February, 2016 17:31:12 > Subject: Re: Upgrading from ACS 4.2 to 4.7 (w/ CEPH) > Hi Lucian, > > Thanks for your email reply. > > We are using Ubuntu instead of CentOS so I guess the "rpm -e" will not be > applicable? My worry is that we are using Ubuntu 12.04 instead of the > Ubuntu 14.04 which is officially supported by ACS 4.7. Anyone has > successfully installed ACS 4.7 or upgraded to ACS 4.7 on Ubuntu 12.04 > environment before? > > Thanks for your recommendation for us to build a staging environment and > for us to wait for 4.7.1 to be released. Any information on when will ACS > version 4.7.1 will be officially released? > > Looking forward to your reply, thank you. > > Cheers. > > -ip- > > > On Sun, Feb 7, 2016 at 5:51 PM, Nux! <[email protected]> wrote: > >> Hello Indra, >> >> I think the procedure is documented here (though not to 4.7, but that >> shouldn't make a difference) >> >> http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgrade-4.2.html >> cloudstack-awsapi has been obsoleted at some point, so before upgrading >> you might want to `rpm -e --nodeps cloudstack-awsapi` >> >> Not sure if the CEPH component will add extra complexity. Perhaps other >> users can advise. >> >> If you do not have a staging environment, then you should build one. I >> have such a thing within a single server with VMs (nested KVM virt), so you >> don't need to mess with multiple physical machines. >> >> In terms of time, it's an operation that - if done manually on a small >> setup - takes less then an hour (assuming fast Internet), but I usually >> reserve the whole day/night for the unexpected. >> >> Reversing your setup is not supported, but I guess it could be done, it >> would've been easier if you ran NFS with simple qcow2 files, though. >> If you take a mysqldump of the management server, a backup of your system >> VMs disks (not sure how you backup/restore CEPH manually); then nothing is >> to stop you to "yum downgrade" and restore your SQL and sysVMs backups or >> just recreating the sysVMs/VRs with the old working template. >> >> Personally I'd wait for 4.7.1 to be released which fixes some bugs. >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> ----- Original Message ----- >> > From: "Indra Pramana" <[email protected]> >> > To: [email protected] >> > Sent: Sunday, 7 February, 2016 08:28:38 >> > Subject: Upgrading from ACS 4.2 to 4.7 >> >> > Dear all, >> > >> > We are currently still using ACS 4.2.0 with KVM hypervisor hosts and Ceph >> > RBD for primary storage. We are planning to upgrade all our management >> and >> > agent servers to ACS 4.7.0 (the latest stable version available on ACS >> > website). >> > >> > >> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.7.0/upgrade/upgrade-4.2.html >> > >> > Anyone has experience in performing the upgrade? Appreciate if anyone can >> > share with me anything I need to take note during the upgrade. >> > >> > - SystemVM template update, is it straightforward or shall I expect any >> > issues along the way? >> > - We are running Ubuntu 12.04 for all our servers, while ACS 4.7 only >> > specifically supports Ubuntu 14.04, can I upgrade to ACS 4.7 without >> having >> > to do "release-upgrade" Ubuntu from 12.04 to 14.04? >> > - Since all the system VMs and virtual routers need to be restarted as >> part >> > of the upgrade, there will be downtime to users. Anyone can advise >> roughly >> > how long it will take for the whole upgrade process so that we can plan >> > accordingly? >> > - If the whole upgrade fails, can we revert back to the original version >> > 4.2? Quite worried that it's not possible since systemVM template and >> > database needs to be upgraded as part of the upgrade. >> > >> > Any other tips / tricks that I need to take note of during the upgrade? >> We >> > do not have any staging / test environment so it's very important for the >> > upgrade to be successful. >> > >> > Any advice is greatly appreciated. >> > >> > Looking forward to your reply, thank you. >> > >> > Cheers. >> > >> > -ip-
