[GitHub] [cloudstack-documentation] Spaceman1984 opened a new pull request #187: Disk provisioning types vmware

[GitBox]

Spaceman1984 opened a new pull request #187:
URL: https://github.com/apache/cloudstack-documentation/pull/187


   Changes related to VMware disk provisioning types.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSS] New default template

[Andrija Panic]

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 
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 
> Sent: 09 June 2020 01:50
> To: us...@cloudstack.apache.org 
> Cc: dev@cloudstack.apache.org ; Abhishek Kumar
> 
> 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.vo...@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 2-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 :
> >
> > 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 
> > Sent: 03 June 2020 13:03
> > To: users 
> > Cc: dev ; 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 consider