My 2 cents: The default template is not there for general or even production use, it’s there for people to 'kick the tires' and either see if CloudStack is what they want or check that their installation is generally OK.
Therefore (IMO) the pre-requisites are: - small download size - compatibility across all of our supported hypervisors - compatibility with all CloudStack features; i.e. live memory and CPU addition, hot disk-pluging, live migrations which require hypervisor tools installed, passing of user-data, meta-data, ssh keys and password resets to the VM via VR and config-drive. - OS commands that users will be relatively familiar with. - ability to be leverage by Marvin tests to perform smoke and integration tests You know - the usual stuff... So that we know that the template should 'always work', I don't think that we should point to an upstream repo, but take an OS version, add/configure whatever is strictly required to meet our requirements, and keep in the CloudStack downloads. Ok, so more like $10 .. Kind regards Paul Angus paul.an...@shapeblue.com www.shapeblue.com 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK @shapeblue -----Original Message----- From: Andrija Panic <andrija.pa...@gmail.com> Sent: 03 June 2020 13:03 To: users <us...@cloudstack.apache.org> Cc: dev <dev@cloudstack.apache.org>; Abhishek Kumar <abhishek.ku...@shapeblue.com> Subject: Re: [DISCUSS] New default template Whatever is a choosen as the new one, needs to be compatible with ALL the current hypervisor we support (i. e. VMware 6.0 and up, XenServer 7.0 and up and KVM of various flavours). So that needs to be taken into consideration when speaking about exotic OS-es or even the newest ones (Ubuntu 20/CentOS 8) to find a proper OS mappings on hypervisor side that will allow it to run normally. On Wed, 3 Jun 2020, 12:21 , <n...@li.nux.ro> wrote: > Hi, > > I'd like to restate my previous stance on this which is - if not to > have a proper "market place" of trusted and tested templates - at > least to cover the popular ones. > The basics imho would be CentOS and Ubuntu, with this we cover 99% of > the user requirements. > I'd propose to go with the latest and greatest of both, Ubuntu 20.04 > and > CentOS8 respectively (supported 2029). > I can repurpose the current build machine for openvm.eu and "donate" > it to the project so it's not a "third party" any more. > > my 2 pence > > On 2020-06-03 08:58, Abhishek Kumar wrote: > > Hi all, > > > > I would like to hear everyone's opinion on a new default template in > > CloudStack. > > Currently, we are using CentOS 5.x for different hypervisors but it > > is quite old(already completed its support life) and either the > > support for it has been removed > > (https://github.com/xcp-ng/xcp/wiki/Guest-System-Support) or in > > legacy ( > https://www.vmware.com/resources/compatibility/search.php?deviceCatego > ry=software&details=1&partner=272&releases=448&page=1&display_interval > =10&sortColumn=Partner&sortOrder=Asc&testConfig=16 > ) > > in different hypervisors. > > Therefore, I think it is time now to move to a newer OS template. In > > my understanding CentOS7 is the minimum viable choice if we are > > continuing with CentOS. This can be the preferred choice as we > > already have tested templates for it on different hypervisors and it > > has 4 years left in its cycle. > > > > We can also explore Ubuntu’s cloud-images of 20.04. And if we want > > to go with something very light-weight we can think about something > > like Alpine Linux. > > > > Please have your say. Also, do you think this can be included in > > 4.15 itself so we can have a proper default template for something > > like XCP-ng 8.x which doesn't support CentOS 5 (and PV VMs)? > > > > Regards, > > Abhishek > > > > > > abhishek.ku...@shapeblue.com > > www.shapeblue.com > > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK > > @shapeblue >
