> On 16 Jul 2019, at 15:02, Adrian Odendaal <adr...@quodes.co.za> wrote: > > Hi There > > I need some help regarding what hardware we can use to get this up and going > as your website indicates only certain cpu’s can be used.
hey where exactly? For running ovirt we support exact same hardware as RHEL/CentOS does > > Kind Regards > > > <bcard.jpg> > > > > > > Legal Disclaimer: > > This message contains privileged and confidential information intended only > for the use of the addressee named above. If you are not the intended > recipient of this message, you are hereby notified that you may not > disseminate, copy or take any action based on the contents thereof; kindly > inform the sender immediately. Any views expressed in this message are those > of the individual sender, except where the sender specifically states them to > be the view of Quodes Solutions CC. While every care has been taken in > preparing this document, no representation, warranty or undertaking > (expressed or implied) is given and no responsibility nor liability is > accepted by any member of Quodes Solutions CC as to the accuracy of the > information contained herein, or for any loss arising from reliance on it. > >> On 15 Jul 2019, at 11:54, Adrian Odendaal <adr...@quodes.co.za >> <mailto:adr...@quodes.co.za>> wrote: >> >> Are those CPU’s dedicated for the Hypervisors? again not sure what you mean. but usually the entire host is dedicated for virtualization >> >> What are the minimal requirements to setting up a cluster? depends what you want it to do. the general a meaningful scale is from cca three hosts up to several hundreds. >> >> We are looking into using Ovirt over the likes on Hyper-v and VMWare. >> >> Can you give me a run down? >> >> Kind Regards >> >> >> <bcard.jpg> >> >> >> >> >> >> Legal Disclaimer: >> >> This message contains privileged and confidential information intended only >> for the use of the addressee named above. If you are not the intended >> recipient of this message, you are hereby notified that you may not >> disseminate, copy or take any action based on the contents thereof; kindly >> inform the sender immediately. Any views expressed in this message are those >> of the individual sender, except where the sender specifically states them >> to be the view of Quodes Solutions CC. While every care has been taken in >> preparing this document, no representation, warranty or undertaking >> (expressed or implied) is given and no responsibility nor liability is >> accepted by any member of Quodes Solutions CC as to the accuracy of the >> information contained herein, or for any loss arising from reliance on it. >> >>> On 15 Jul 2019, at 11:23, Michal Skrivanek <michal.skriva...@redhat.com >>> <mailto:michal.skriva...@redhat.com>> wrote: >>> >>> >>> >>>> On 15 Jul 2019, at 09:38, Emil Natan <e...@redhat.com >>>> <mailto:e...@redhat.com>> wrote: >>>> >>>> I think the right place for this question is the ovirt users mailing list. >>>> Added. >>>> >>>> On Mon, Jul 15, 2019 at 10:28 AM <adr...@quodes.co.za >>>> <mailto:adr...@quodes.co.za>> wrote: >>>> Hi All >>>> >>>> We are looking into setting up a highly scalable and HA Ovirt >>>> infrastructure but I see only some CPU's are supported. Is this only for >>>> th Hypervisors or for the entire cluster? >>> >>> Not sure what difference you have in mind. In general those are for guest >>> CPUs, in general KVM capabilities are a bit behind the real hardware and >>> gets added to oVirt as we add the relevant qemu-kvm having them, e.g. right >>> now the “best” x86_64 Intel CPU is Skylake-Server and you can run it on any >>> RHEL/CentOS 7.6 supported hw capable of at least that, e.g. any Cascade >>> Lake. >>> >>>> _______________________________________________ >>>> Infra mailing list -- in...@ovirt.org <mailto:in...@ovirt.org> >>>> To unsubscribe send an email to infra-le...@ovirt.org >>>> <mailto:infra-le...@ovirt.org> >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> <https://www.ovirt.org/site/privacy-policy/> >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> <https://www.ovirt.org/community/about/community-guidelines/> >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/in...@ovirt.org/message/X5MMJXN67LMBCJQKDPK4MJECHMQWVKXZ/ >>>> >>>> <https://lists.ovirt.org/archives/list/in...@ovirt.org/message/X5MMJXN67LMBCJQKDPK4MJECHMQWVKXZ/> >>>> >>>> >>>> -- >>>> Emil Natan >>>> RHV/CNV DevOps >>>> _______________________________________________ >>>> Infra mailing list -- in...@ovirt.org <mailto:in...@ovirt.org> >>>> To unsubscribe send an email to infra-le...@ovirt.org >>>> <mailto:infra-le...@ovirt.org> >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> <https://www.ovirt.org/site/privacy-policy/> >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> <https://www.ovirt.org/community/about/community-guidelines/> >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/in...@ovirt.org/message/H62H2FA2DBEUF6CENHXTWVR6GEXVCYCX/ >>>> >>>> <https://lists.ovirt.org/archives/list/in...@ovirt.org/message/H62H2FA2DBEUF6CENHXTWVR6GEXVCYCX/> >>> >> >
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XN5TU5SMZHXHQ55JZRNARD32UG3GU362/
