You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Abhishek Kumar <Ab...@shapeblue.com> on 2020/06/03 07:58:56 UTC
[DISCUSS] New default template
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?deviceCategory=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.Kumar@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
Re: [DISCUSS] New default template
Posted by Rohit Yadav <ro...@shapeblue.com>.
We've discussed this in the past:
https://markmail.org/message/lp5pjholfxrqhful
https://markmail.org/message/mkoasohxr5vwyt3l
We probably want both CentOS and Ubuntu based built-in (or default user) templates, and some people may even prefer Debian, Fedora or even FreeBSD.
I think it would simpler if the built-in template is a single template and based on DistroWatch [1] it seems a Debian based OS may be more preferable for most users.
Therefore, either a LTS version of Ubuntu (say Ubuntu 20.04) or even Debian is preferable. The cons of this decision would be to test and fix many smoke tests and component tests.
If we prefer Debian (latest LTS), we can actually make the systemvmtemplate cloud-init enabled and use it both as the template for system vms but also guest VMs. For every release, we won't need to maintain two separate templates (a systemvmtemplate and a built-in template) and revisit this issue again in say next 5 years. A Debian (latest LTS) based built-in template may even serve for the CKS feature (so if this is do-able and done right, we'll solve the template issue for systemvms, built-in template and CKS).
To summarise:
* A CentOS7 based (cloud-init enabled) built-in template would be easiest thing to do (in terms of effort and testing); we already have the packer script that we needs an update - https://github.com/apache/cloudstack/tree/master/tools/appliance/builtin
* An Ubuntu 20.04 current/LTS based (cloud-init) template would be something that most users would want; but adds effort on fixing integration tests
* A Debian LTS based (cloud-init) template would add effort on fixing integration tests but would serve most of our requirements which I think are:
* Users prefer a Debian/Ubuntu based guest OS
* The template can be cloud-init enabled to work out of box for SSH acccess
* We already have the packer script (https://github.com/apache/cloudstack/tree/master/tools/appliance/systemvmtemplate) that we can extend to build a single template to serve for systemvmtemplate, built-in template and template for CKS as:
* Replace and refactor cloud-early-config with a cloud-init equivalent
* Install hypervisor-specific guest tools (we already do this for systemvmtemplate)
* Remove noncommon packages and instead either build that as a docker image (tar file) or deb files bundled in systemvm.iso (such as JRE, strongswan, docker etc)
* Debian templates are big in size, to keep the template size very small and further improve how systemvmtemplates are seeded, we can explore Alpine Linux (or similar?)
[1] https://distrowatch.com/dwres.php?resource=popularity
Regards,
Rohit Yadav
Software Architect, ShapeBlue
https://www.shapeblue.com
________________________________
From: Abhishek Kumar <Ab...@shapeblue.com>
Sent: Wednesday, June 3, 2020 13:28
To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
Cc: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: [DISCUSS] New default template
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?deviceCategory=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.Kumar@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
Re: [DISCUSS] New default template
Posted by Andrija Panic <an...@gmail.com>.
Debian does sound like a possible choice, considering the CentOS changes.
Note that Debian 10 is only supported starting from vSphere 6.7U2, and
XenServer 8.1, so different OS mapping need to be in place to support older
hypervisors (Other Linux 64-bit etc) - to ensure a somewhat proper OS
functioning - and of course, to be tested across all support hypervisors.
On Mon, 25 Jan 2021 at 13:10, Abhishek Kumar <Ab...@shapeblue.com>
wrote:
> Hi all,
>
> Can we have a consensus on this and maybe discuss options again
> considering CentOS changes [1].
> It will be great if we can decide and get something new in 4.16, thoughts?
> With upcoming CKS changes [2], Debian can make a good choice.
>
> Regards,
> Abhishek
>
>
> [1] https://blog.centos.org/2020/12/future-is-centos-stream/
> [2] https://github.com/apache/cloudstack/pull/4329
>
> ________________________________
> From: Sven Vogel <S....@ewerk.com>
> Sent: 09 June 2020 01:50
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Cc: dev@cloudstack.apache.org <de...@cloudstack.apache.org>; Abhishek Kumar
> <Ab...@shapeblue.com>
> Subject: Re: [DISCUSS] New default template
>
> My small additions.
>
> I would go with an LTS version.
>
> For me it would be CentOS 8 minimal. I agree with Paul sometimes the
> upstream repo are gone or in archive state and its not for production use.
> Maybe we can put one of them to „our“ Cloudstack repo. If we use Ubuntu or
> CentOS is not so important both are LTS versions.
>
> Maybe we should find a regular way after some time to switch to a newer
> one. So there is no productive use and normally everybody should know that
> he don’t use this in a production environment. We can’t address all
> security issues from the os. Maybe we should hint the users and at the end
> of the day its their own risk if they use this.
>
> Cheers
>
> Sven
>
>
>
>
>
> __
>
> Sven Vogel
> Lead Cloud Solution Architect
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> S.Vogel@ewerk.com
> www.ewerk.com<http://www.ewerk.com>
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> Registergericht: Leipzig HRB 9065
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 08.06.2020 um 16:21 schrieb Paul Angus <pa...@shapeblue.com>:
> >
> > 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.angus@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >
> > -----Original Message-----
> > From: Andrija Panic <an...@gmail.com>
> > Sent: 03 June 2020 13:03
> > To: users <us...@cloudstack.apache.org>
> > Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <
> Abhishek.Kumar@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 , <nu...@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.Kumar@shapeblue.com
> >>> www.shapeblue.com<http://www.shapeblue.com>
> >>> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> >>> @shapeblue
> >>
>
>
> Abhishek.Kumar@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
--
Andrija Panić
Re: [DISCUSS] New default template
Posted by Andrija Panic <an...@gmail.com>.
Debian does sound like a possible choice, considering the CentOS changes.
Note that Debian 10 is only supported starting from vSphere 6.7U2, and
XenServer 8.1, so different OS mapping need to be in place to support older
hypervisors (Other Linux 64-bit etc) - to ensure a somewhat proper OS
functioning - and of course, to be tested across all support hypervisors.
On Mon, 25 Jan 2021 at 13:10, Abhishek Kumar <Ab...@shapeblue.com>
wrote:
> Hi all,
>
> Can we have a consensus on this and maybe discuss options again
> considering CentOS changes [1].
> It will be great if we can decide and get something new in 4.16, thoughts?
> With upcoming CKS changes [2], Debian can make a good choice.
>
> Regards,
> Abhishek
>
>
> [1] https://blog.centos.org/2020/12/future-is-centos-stream/
> [2] https://github.com/apache/cloudstack/pull/4329
>
> ________________________________
> From: Sven Vogel <S....@ewerk.com>
> Sent: 09 June 2020 01:50
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Cc: dev@cloudstack.apache.org <de...@cloudstack.apache.org>; Abhishek Kumar
> <Ab...@shapeblue.com>
> Subject: Re: [DISCUSS] New default template
>
> My small additions.
>
> I would go with an LTS version.
>
> For me it would be CentOS 8 minimal. I agree with Paul sometimes the
> upstream repo are gone or in archive state and its not for production use.
> Maybe we can put one of them to „our“ Cloudstack repo. If we use Ubuntu or
> CentOS is not so important both are LTS versions.
>
> Maybe we should find a regular way after some time to switch to a newer
> one. So there is no productive use and normally everybody should know that
> he don’t use this in a production environment. We can’t address all
> security issues from the os. Maybe we should hint the users and at the end
> of the day its their own risk if they use this.
>
> Cheers
>
> Sven
>
>
>
>
>
> __
>
> Sven Vogel
> Lead Cloud Solution Architect
>
> EWERK DIGITAL GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> S.Vogel@ewerk.com
> www.ewerk.com<http://www.ewerk.com>
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> Registergericht: Leipzig HRB 9065
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 08.06.2020 um 16:21 schrieb Paul Angus <pa...@shapeblue.com>:
> >
> > 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.angus@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >
> > -----Original Message-----
> > From: Andrija Panic <an...@gmail.com>
> > Sent: 03 June 2020 13:03
> > To: users <us...@cloudstack.apache.org>
> > Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <
> Abhishek.Kumar@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 , <nu...@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.Kumar@shapeblue.com
> >>> www.shapeblue.com<http://www.shapeblue.com>
> >>> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> >>> @shapeblue
> >>
>
>
> Abhishek.Kumar@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
--
Andrija Panić
Re: [DISCUSS] New default template
Posted by Abhishek Kumar <Ab...@shapeblue.com>.
Hi all,
Can we have a consensus on this and maybe discuss options again considering CentOS changes [1].
It will be great if we can decide and get something new in 4.16, thoughts?
With upcoming CKS changes [2], Debian can make a good choice.
Regards,
Abhishek
[1] https://blog.centos.org/2020/12/future-is-centos-stream/
[2] https://github.com/apache/cloudstack/pull/4329
________________________________
From: Sven Vogel <S....@ewerk.com>
Sent: 09 June 2020 01:50
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: dev@cloudstack.apache.org <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@shapeblue.com>
Subject: Re: [DISCUSS] New default template
My small additions.
I would go with an LTS version.
For me it would be CentOS 8 minimal. I agree with Paul sometimes the upstream repo are gone or in archive state and its not for production use. Maybe we can put one of them to „our“ Cloudstack repo. If we use Ubuntu or CentOS is not so important both are LTS versions.
Maybe we should find a regular way after some time to switch to a newer one. So there is no productive use and normally everybody should know that he don’t use this in a production environment. We can’t address all security issues from the os. Maybe we should hint the users and at the end of the day its their own risk if they use this.
Cheers
Sven
__
Sven Vogel
Lead Cloud Solution Architect
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com
www.ewerk.com<http://www.ewerk.com>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2011
EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank.
The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you.
> Am 08.06.2020 um 16:21 schrieb Paul Angus <pa...@shapeblue.com>:
>
> 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.angus@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 03 June 2020 13:03
> To: users <us...@cloudstack.apache.org>
> Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@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 , <nu...@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.Kumar@shapeblue.com
>>> www.shapeblue.com<http://www.shapeblue.com>
>>> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
>>> @shapeblue
>>
Abhishek.Kumar@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
Re: [DISCUSS] New default template
Posted by Abhishek Kumar <Ab...@shapeblue.com>.
Hi all,
Can we have a consensus on this and maybe discuss options again considering CentOS changes [1].
It will be great if we can decide and get something new in 4.16, thoughts?
With upcoming CKS changes [2], Debian can make a good choice.
Regards,
Abhishek
[1] https://blog.centos.org/2020/12/future-is-centos-stream/
[2] https://github.com/apache/cloudstack/pull/4329
________________________________
From: Sven Vogel <S....@ewerk.com>
Sent: 09 June 2020 01:50
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: dev@cloudstack.apache.org <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@shapeblue.com>
Subject: Re: [DISCUSS] New default template
My small additions.
I would go with an LTS version.
For me it would be CentOS 8 minimal. I agree with Paul sometimes the upstream repo are gone or in archive state and its not for production use. Maybe we can put one of them to „our“ Cloudstack repo. If we use Ubuntu or CentOS is not so important both are LTS versions.
Maybe we should find a regular way after some time to switch to a newer one. So there is no productive use and normally everybody should know that he don’t use this in a production environment. We can’t address all security issues from the os. Maybe we should hint the users and at the end of the day its their own risk if they use this.
Cheers
Sven
__
Sven Vogel
Lead Cloud Solution Architect
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com
www.ewerk.com<http://www.ewerk.com>
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2011
EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank.
The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you.
> Am 08.06.2020 um 16:21 schrieb Paul Angus <pa...@shapeblue.com>:
>
> 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.angus@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 03 June 2020 13:03
> To: users <us...@cloudstack.apache.org>
> Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@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 , <nu...@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.Kumar@shapeblue.com
>>> www.shapeblue.com<http://www.shapeblue.com>
>>> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
>>> @shapeblue
>>
Abhishek.Kumar@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
Re: [DISCUSS] New default template
Posted by Sven Vogel <S....@ewerk.com>.
My small additions.
I would go with an LTS version.
For me it would be CentOS 8 minimal. I agree with Paul sometimes the upstream repo are gone or in archive state and its not for production use. Maybe we can put one of them to „our“ Cloudstack repo. If we use Ubuntu or CentOS is not so important both are LTS versions.
Maybe we should find a regular way after some time to switch to a newer one. So there is no productive use and normally everybody should know that he don’t use this in a production environment. We can’t address all security issues from the os. Maybe we should hint the users and at the end of the day its their own risk if they use this.
Cheers
Sven
__
Sven Vogel
Lead Cloud Solution Architect
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com
www.ewerk.com
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2011
EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank.
The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you.
> Am 08.06.2020 um 16:21 schrieb Paul Angus <pa...@shapeblue.com>:
>
> 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.angus@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 03 June 2020 13:03
> To: users <us...@cloudstack.apache.org>
> Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@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 , <nu...@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.Kumar@shapeblue.com
>>> www.shapeblue.com
>>> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
>>> @shapeblue
>>
Re: [DISCUSS] New default template
Posted by Andrija Panic <an...@gmail.com>.
I agree with Paul - a single, well-configured one.
(Considering the Marvin tests are run using the current default template, I
think it might make sense to consider CentOS 7/8, bug again, just
my opinion)
On Mon, 8 Jun 2020 at 16:22, Paul Angus <pa...@shapeblue.com> wrote:
> 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.angus@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 03 June 2020 13:03
> To: users <us...@cloudstack.apache.org>
> Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <
> Abhishek.Kumar@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 , <nu...@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.Kumar@shapeblue.com
> > > www.shapeblue.com
> > > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > > @shapeblue
> >
>
--
Andrija Panić
Re: [DISCUSS] New default template
Posted by Sven Vogel <S....@ewerk.com>.
My small additions.
I would go with an LTS version.
For me it would be CentOS 8 minimal. I agree with Paul sometimes the upstream repo are gone or in archive state and its not for production use. Maybe we can put one of them to „our“ Cloudstack repo. If we use Ubuntu or CentOS is not so important both are LTS versions.
Maybe we should find a regular way after some time to switch to a newer one. So there is no productive use and normally everybody should know that he don’t use this in a production environment. We can’t address all security issues from the os. Maybe we should hint the users and at the end of the day its their own risk if they use this.
Cheers
Sven
__
Sven Vogel
Lead Cloud Solution Architect
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
S.Vogel@ewerk.com
www.ewerk.com
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065
Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2011
EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank.
The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you.
> Am 08.06.2020 um 16:21 schrieb Paul Angus <pa...@shapeblue.com>:
>
> 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.angus@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 03 June 2020 13:03
> To: users <us...@cloudstack.apache.org>
> Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@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 , <nu...@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.Kumar@shapeblue.com
>>> www.shapeblue.com
>>> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
>>> @shapeblue
>>
Re: [DISCUSS] New default template
Posted by Andrija Panic <an...@gmail.com>.
I agree with Paul - a single, well-configured one.
(Considering the Marvin tests are run using the current default template, I
think it might make sense to consider CentOS 7/8, bug again, just
my opinion)
On Mon, 8 Jun 2020 at 16:22, Paul Angus <pa...@shapeblue.com> wrote:
> 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.angus@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Andrija Panic <an...@gmail.com>
> Sent: 03 June 2020 13:03
> To: users <us...@cloudstack.apache.org>
> Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <
> Abhishek.Kumar@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 , <nu...@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.Kumar@shapeblue.com
> > > www.shapeblue.com
> > > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > > @shapeblue
> >
>
--
Andrija Panić
RE: [DISCUSS] New default template
Posted by Paul Angus <pa...@shapeblue.com>.
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.angus@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>
Sent: 03 June 2020 13:03
To: users <us...@cloudstack.apache.org>
Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@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 , <nu...@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.Kumar@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > @shapeblue
>
RE: [DISCUSS] New default template
Posted by Paul Angus <pa...@shapeblue.com>.
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.angus@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Andrija Panic <an...@gmail.com>
Sent: 03 June 2020 13:03
To: users <us...@cloudstack.apache.org>
Cc: dev <de...@cloudstack.apache.org>; Abhishek Kumar <Ab...@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 , <nu...@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.Kumar@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > @shapeblue
>
Re: [DISCUSS] New default template
Posted by Andrija Panic <an...@gmail.com>.
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 , <nu...@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?deviceCategory=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.Kumar@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > @shapeblue
>
Re: [DISCUSS] New default template
Posted by Andrija Panic <an...@gmail.com>.
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 , <nu...@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?deviceCategory=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.Kumar@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> > @shapeblue
>
Re: [DISCUSS] New default template
Posted by nu...@li.nux.ro.
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?deviceCategory=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.Kumar@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
Re: [DISCUSS] New default template
Posted by nu...@li.nux.ro.
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?deviceCategory=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.Kumar@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
Re: [DISCUSS] New default template
Posted by Rohit Yadav <ro...@shapeblue.com>.
We've discussed this in the past:
https://markmail.org/message/lp5pjholfxrqhful
https://markmail.org/message/mkoasohxr5vwyt3l
We probably want both CentOS and Ubuntu based built-in (or default user) templates, and some people may even prefer Debian, Fedora or even FreeBSD.
I think it would simpler if the built-in template is a single template and based on DistroWatch [1] it seems a Debian based OS may be more preferable for most users.
Therefore, either a LTS version of Ubuntu (say Ubuntu 20.04) or even Debian is preferable. The cons of this decision would be to test and fix many smoke tests and component tests.
If we prefer Debian (latest LTS), we can actually make the systemvmtemplate cloud-init enabled and use it both as the template for system vms but also guest VMs. For every release, we won't need to maintain two separate templates (a systemvmtemplate and a built-in template) and revisit this issue again in say next 5 years. A Debian (latest LTS) based built-in template may even serve for the CKS feature (so if this is do-able and done right, we'll solve the template issue for systemvms, built-in template and CKS).
To summarise:
* A CentOS7 based (cloud-init enabled) built-in template would be easiest thing to do (in terms of effort and testing); we already have the packer script that we needs an update - https://github.com/apache/cloudstack/tree/master/tools/appliance/builtin
* An Ubuntu 20.04 current/LTS based (cloud-init) template would be something that most users would want; but adds effort on fixing integration tests
* A Debian LTS based (cloud-init) template would add effort on fixing integration tests but would serve most of our requirements which I think are:
* Users prefer a Debian/Ubuntu based guest OS
* The template can be cloud-init enabled to work out of box for SSH acccess
* We already have the packer script (https://github.com/apache/cloudstack/tree/master/tools/appliance/systemvmtemplate) that we can extend to build a single template to serve for systemvmtemplate, built-in template and template for CKS as:
* Replace and refactor cloud-early-config with a cloud-init equivalent
* Install hypervisor-specific guest tools (we already do this for systemvmtemplate)
* Remove noncommon packages and instead either build that as a docker image (tar file) or deb files bundled in systemvm.iso (such as JRE, strongswan, docker etc)
* Debian templates are big in size, to keep the template size very small and further improve how systemvmtemplates are seeded, we can explore Alpine Linux (or similar?)
[1] https://distrowatch.com/dwres.php?resource=popularity
Regards,
Rohit Yadav
Software Architect, ShapeBlue
https://www.shapeblue.com
________________________________
From: Abhishek Kumar <Ab...@shapeblue.com>
Sent: Wednesday, June 3, 2020 13:28
To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
Cc: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: [DISCUSS] New default template
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?deviceCategory=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.Kumar@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
rohit.yadav@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue