[ovirt-users] Re: Ovirt vs RHEV
Hi, Red Hat has a upstream first policy meaning that in terms of code there is no difference. The main differences of a RHV subscription are: 1. Longer support life cycle and ELS/EUS options with a security first priorities. 2. Access to support with different levels on SLA options. 3. More stabilization cycles based on QA testing. 4. Certification to partners, HW, security standards and other open source products. The goals in this are to improve cost efficiencies, security and predictability, in order to allowing customers to contribute back to community development and innovation. Thanks, YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. <https://www.redhat.com/> 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 yl...@redhat.comT: +972-9-7692306/8272306 F: +972-9-7692223IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> On Mon, Jul 2, 2018 at 2:08 PM Krzysztof Wajda wrote: > Hi, > > can anyone explain differences between Ovirt and RHEV in version 4.1 ? I > know that RHEV has diffrent product life-cycle, and there are some > diffrences in installation process. Do you know if there are any > additional featuers in Ovirt or RHEV ? Do you know any oifficial statements > from RH about differences ? From my experience there is not too much > diffrences, but I need to prepere such a comaprison for bussines so I > would like to get an info from relaiable source. > > > Chris > ___ > 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/TP3MNCO3WUC5OYQPZOMUOB4GONBBQCOM/ > ___ 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/ST27DHLKARDO3JVTSC4JVVS7DBDZRIFL/
Re: [ovirt-users] oVirt Survey 2018 results
YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. <https://www.redhat.com/> 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 yl...@redhat.comT: +972-9-7692306/8272306 F: +972-9-7692223IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> On Sun, Feb 25, 2018 at 4:00 PM, Yaniv Lavi wrote: > Some notes that may help the users based on the replies on the survey > (based on latest 4.2): > > - ISO upload to storage domain is supported (UI/API). Can be used just > like disk upload and it supports quota based on the disk used. > > - You now have partial incremental backup support with download/upload API > (at long as the snapshot still exists): >https://ovirt.org/develop/release-management/features/ > storage/backup-restore-disk-snapshots/ > > - You can now download/upload VMs from data storage domains. > > Correction: > - VM keep their compatibility version after cluster version upgrade, so it > is ok to not restart in upgrade (at least until CentOS 8). > > - Ceph can be used with ISCSI target with oVirt. > > - macspoofing hook is not really needed in oVirt 4.x, this is a supported > feature that can be used in vNIC profiles. > > - Some of the users change migration settings in VDSM. This is not really > needed with oVirt 4.2 and migration policies which less error prone and > more advanced. > > Hope this helps some of you. > > > Thanks! > > > YANIV LAVI > > SENIOR TECHNICAL PRODUCT MANAGER > > Red Hat Israel Ltd. <https://www.redhat.com/> > > 34 Jerusalem Road, Building A, 1st floor > > Ra'anana, Israel 4350109 > > yl...@redhat.comT: +972-9-7692306/8272306 F: +972-9-7692223IM: > ylavi > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > @redhatnews <https://twitter.com/redhatnews> Red Hat > <https://www.linkedin.com/company/red-hat> Red Hat > <https://www.facebook.com/RedHatInc> > > > On Fri, Feb 2, 2018 at 11:22 AM, Sandro Bonazzola > wrote: > >> Thank you very much for having participated in oVirt Survey 2018! >> Results are now publicly available at http://bit.ly/2Ez909d >> We're now analyzing results for 4.3 planning. >> >> -- >> >> SANDRO BONAZZOLA >> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >> >> Red Hat EMEA <https://www.redhat.com/> >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt Survey 2018 results
Some notes that may help the users based on the replies on the survey (based on latest 4.2): - ISO upload to storage domain is supported (UI/API). Can be used just like disk upload and it supports quota based on the disk used. - You now have partial incremental backup support with download/upload API (at long as the snapshot still exists): https://ovirt.org/develop/release-management/features/storage/backup-restore-disk-snapshots/ - You can now download/upload VMs from data storage domains. - VM not keep their compatibility version after cluster version upgrade, so it is ok to not restart in upgrade (at least until CentOS 8). - Ceph can be used with ISCSI target with oVirt. - macspoofing hook is not really needed in oVirt 4.x, this is a supported feature that can be used in vNIC profiles. - Some of the users change migration settings in VDSM. This is not really needed with oVirt 4.2 and migration policies which less error prone and more advanced. Hope this helps some of you. Thanks! YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. <https://www.redhat.com/> 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 yl...@redhat.comT: +972-9-7692306/8272306 F: +972-9-7692223IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> On Fri, Feb 2, 2018 at 11:22 AM, Sandro Bonazzola wrote: > Thank you very much for having participated in oVirt Survey 2018! > Results are now publicly available at http://bit.ly/2Ez909d > We're now analyzing results for 4.3 planning. > > -- > > SANDRO BONAZZOLA > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] deprecating export domain?
Please open RFE requests for your suggestions. thanks, YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. <https://www.redhat.com/> 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 yl...@redhat.comT: +972-9-7692306/8272306 F: +972-9-7692223IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> On Tue, Oct 3, 2017 at 6:38 PM, Pavel Gashev wrote: > Shubham, > > > > I hope you’re going to keep the Export feature at least as “Clone to > another storage domain”. In the real life, the copy-in/copy-out is required > for backups. Moving disks between Data SD and Backup SD is not a way to > backup or restore. It’s often required to keep VM runnable during backing > up, and it’s often required to keep a backup during restoring. Typical > backup storage is not designed for running VMs directly. SSDs are not cheap > enough for storing backups, and there are HDDs especially designed for > storing cold data [1]. Thus, the disaster recovery scenario is a great > feature, but it can’t be a recommended way to recover. > > > > And I hope you are going to show VMs on backup storages in a separate list > (“Backups” instead of “Virtual Machines”). > > > > [1] http://www.seagate.com/enterprise-storage/hard-disk- > drives/archive-hdd/ > > > > I hope this helps. > > > > *From: *shubham dubey > *Date: *Monday, 2 October 2017 at 19:10 > *To: *Pavel Gashev > *Cc: *Maor Lipchuk , "users@ovirt.org" < > users@ovirt.org> > > *Subject: *Re: [ovirt-users] deprecating export domain? > > > > Yes, I just gave an example case. If you want to use vms with a backup, > then you can just copy that vm or disk into another domain and make it as > backup domain as you do it in export domain. > > In simple language, main aim of creating backup domain is just to use all > the features available in export domain without creating a dedicated export > domain. > > Hope you understand now:) > > > > > > > > On 2 Oct 2017 8:55 pm, "Pavel Gashev" wrote: > > Shubham, > > > > I don’t really understand the process you described. If I need to backup > the whole datacenter, you say I have to turn off all VMs, and make them > non-runnable. It doesn’t look like a backing up. It looks like an > archiving. But what if I need to keep my VMs running? > > > > > > *From: *shubham dubey > *Date: *Monday, 2 October 2017 at 15:55 > *To: *Charles Kozler > *Cc: *Pavel Gashev , users , Maor > Lipchuk > *Subject: *Re: [ovirt-users] deprecating export domain? > > > > Hi, > > The backup storage domain is quite like export storage domain but with > easy usability. > > Since you can change any data domain into backup domain any time, you not > need to create a dedicated > > export storage domain for backup or disaster recovery purpose. Altough its > working is same as export sd. > > The process of backup can be as simple as this: > > 1) turn off all the vms in your storage domain > > 2) select backup flag to convert that into backup domain. > > Once the domain is used for backup, you cannot make any changes to its > vms, disk etc as mentioned by maor. > > And yes, you can convert export sd to data domain using cli script but it > is not required anymore. > > If in future export storage domain get deprecated, you not need to be > worry about that much since you can convert all your > > export sd into data domain anytime and start using backup feature instead. > > Regards, > > Shubham > > > > > > On Mon, Oct 2, 2017 at 6:04 PM, Charles Kozler > wrote: > > Thank you for clearing this up for me everyone. My concern that something > like the export domain wasnt going to exist and it was just going to be > deprecated with no alternative. Glad to hear all the news of the SD > > > > On Mon, Oct 2, 2017 at 8:31 AM, Pavel Gashev wrote: > > Maor, > > Could you please clarify, what would be the process of making backup of a > running VM to an existing backup storage domain? > > I’m asking because it looks like the process is going to be quite the same: > 1. Clone VM from a snapshot > 2. Move the cloned VM to a backup storage domain > > An ability of choosing destination storage for cloned VMs would increase > backup efficiency. On the other hand, an ability of exporting VM from a > snapshot would increase the efficiency in the same way even without > creating new entity. > > I
Re: [ovirt-users] oVIRT Node / Network Manager / oVirt 4.1
oVirt can co-exist with NM. No reason to turn it off. YANIV LAVI (YANIV DARY) SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. <https://www.redhat.com/> 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 yl...@redhat.comT: +972-9-7692306/8272306 F: +972-9-7692223IM: ylavi <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> On Mon, Jul 31, 2017 at 9:16 PM, Devin Acosta wrote: > > I noticed that for some reason when I am running oVirt node on my hosts > and disabled NetworkManager it appears that it kept turning itself back on, > and my understanding is that Network Manager should be disabled. I had to > force remove Network Manager in order to get it to stay disabled. I have > been seeing strangeness with my VM's where they disconnect, and where > hosted-engine keeps trying to non-stop migrate to another host. Just wanted > to first confirm about Network Manager and oVirt Node image. > > -- > > Devin Acosta > Red Hat Certified Architect > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
