Hi Hean, Yes I think the old approach of registering systemvm template prior to upgrade as well as the option to switch between systemvmtemplate continues to be supported. What this feature primarily aims is to make CloudStack turnkey operationally.
May I ask if anyone has any objections on the increased package size? Due to the trade off of including systemvmtemplates in the management package the size increased to about 1-1.5GB which is the only thing I didn't like. However I think this can be optimised in future releases. Regards. ________________________________ From: Hean Seng <heans...@gmail.com> Sent: Thursday, September 2, 2021 7:34:32 AM To: us...@cloudstack.apache.org <us...@cloudstack.apache.org> Cc: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: Re: [DISCUSS] SystemVM template upgrade improvements This is good idea. Or else , we shall allow manual upload via. GUI, and mark for system template . On Wed, Sep 1, 2021 at 9:08 PM Pearl d'Silva <pearl.dsi...@shapeblue.com> wrote: > I probably missed adding the PR link to the feature - > https://github.com/apache/cloudstack/pull/4329. Please do provide you > inputs. > > > Thanks, > Pearl > > ________________________________ > From: Pearl d'Silva <pearl.dsi...@shapeblue.com> > Sent: Wednesday, September 1, 2021 5:49 PM > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: [DISCUSS] SystemVM template upgrade improvements > > Hi All, > > We have been working on a feature that simplifies SystemVM template > install and upgrades for CloudStack. Historically we've required users to > seed the template on secondary storage during fresh installation and > register the template before an upgrade - this really does not make > CloudStack turnkey, as we end up maintaining and managing them as a > separate component - for example, users can't simply do an apt-get upgrade > or yum upgrade to upgrade CloudStack. > > The feature works by automatically initiating registration of the SystemVM > templates during upgrades or when the first secondary storage is added to a > zone where the SystemVM template hasn't been seeded. This feature addresses > several operational pain points for example, when the admin user forgets to > register the SystemVM template prior to an upgrade and faces the issue of > having to roll back the database midway during the upgrade process. With > this feature the upgrade process is seamless, such that the end users do > not need to worry about having to perform template registration, but rather > have the upgrade process take care of everything that is required. > > In order to facilitate this feature, the SystemVM templates have to be > bundled with the cloudstack-management rpm/deb package which causes the > total noredist cloudstack-management package size to increase to about > 1.6GB. We currently are packaging templates of only the three widely > supported hypervisors - KVM, XenServer/XCP-ng and VMWare. > (These templates are only packaged if the build is initiated with the > noredist flag.) > > We'd like to get your opinion on this idea. > > Thanks & Regards, > Pearl Dsilva > > > > > > > -- Regards, Hean Seng
