[ovirt-devel] Re: Questions for Redhat team

2018-12-13 Thread Nir Soffer 
On Thu, Dec 13, 2018 at 3:24 PM Suchitra Herwadkar <
suchitra.herwad...@veritas.com> wrote:

> Hi Nir & RedHat team
>
>
>
>1. Cloned VM support in RHV.
>
> There are two types of clones as per my understanding
>
>1. Full Cloned VM: Independent copy of a virtual machine that shares
>nothing with the parent template after the cloning operation.
>2. Dependent Cloned VM: It is a copy of a virtual machine that shares
>virtual disks with the parent template. This type of clone is made from a
>snapshot of the parent which is qcow2 image. All files available on the
>parent at the moment of the snapshot continue to remain available to the
>linked clone. Ongoing changes to the virtual disk of the parent do not
>affect the linked clone, and changes to the disk of the linked clone do not
>affect the parent.
>
>
>
> We want to know what the customer preference ( 1 or 2) as both have pros &
> cons. What is the guidance given by RHV around this?  How do we recommend
> customers to patch the template disks when multiple VMs are cloned from
> it?  Kindly provide more details.
>

Customer can use both types of clones, based on their needs. If having the
dependency on the
a shared template is fine, and the user is ok with having qcow2 format and
at least one snapshot,
and prefer faster cloning, they can go with this option.

If the user wants to use raw format which can give better performance, and
ok with waiting for
a slower clone, copying all the data to new image, they can go with full
clone.

So I think on your side you should support both options, so users can make
the best choice for their
needs.

>
>
>1. Is there a way to we can mount a QCOW2 image using QCOW2 mounter
>and have a block level view of the data ?  We read about libguestfs but
>this is filesystem view.
>
>
In 4.3 we will use NBD protocol to allow block level view of an image,
including all snapshots.

You will be able to do full or incremental backup, or restore raw data to
qcow2 image.
See:
https://ovirt.org/develop/release-management/features/storage/incremental-backup/#backup-rest-api


>
>1. We would like to know when we can expect “Allocation Regions API” .
>I’m referring to
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1622946
>
This is part of incremental backup effort:
https://ovirt.org/develop/release-management/features/storage/incremental-backup/#imageio-backup-api

> This is marked for 4.3 at this point in time.  I presume we will get it as
> part of 4.2.X release as well.
>
No, this requires major changes in engine, vdsm and imageio, which will be
available only in 4.3.

The new API is documented here:
https://ovirt.org/develop/release-management/features/storage/incremental-backup/#imageio-backup-api

We would like to get early feedback, before we implement it.

Nir

>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/Q35UJD7CVTWOLPCUBQ5FPIMNPGLGAUWX/

[ovirt-devel] Re: propose Ravi Nori as a frontend maintainer for ovirt-engine infra

2018-12-13 Thread Sandro Bonazzola 
Il giorno lun 10 dic 2018 alle ore 16:23 Greg Sheremeta 
ha scritto:

> Hi all,
>
> I'd like to propose Ravi Nori as a frontend maintainer for ovirt-engine
> infra team. While the infra team typically hasn't had a frontend
> maintainer, Ravi has strong knowledge of all of the frontend infra pieces,
> including everything related to SSO, welcome page, and GWT in admin portal.
>

+1


>
> Best wishes,
> Greg
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-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/devel@ovirt.org/message/Z5MOEX5A72X355LL3G2LOFM6U7AS6ZFI/
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/CI6ZP4VCSWYMRIM34DTY6KZS54MRJXXC/

[ovirt-devel] Questions for Redhat team

2018-12-13 Thread Suchitra Herwadkar 
Hi Nir & RedHat team


  1.  Cloned VM support in RHV.

There are two types of clones as per my understanding

  1.  Full Cloned VM: Independent copy of a virtual machine that shares nothing 
with the parent template after the cloning operation.
  2.  Dependent Cloned VM: It is a copy of a virtual machine that shares 
virtual disks with the parent template. This type of clone is made from a 
snapshot of the parent which is qcow2 image. All files available on the parent 
at the moment of the snapshot continue to remain available to the linked clone. 
Ongoing changes to the virtual disk of the parent do not affect the linked 
clone, and changes to the disk of the linked clone do not affect the parent.



We want to know what the customer preference ( 1 or 2) as both have pros & 
cons. What is the guidance given by RHV around this?  How do we recommend 
customers to patch the template disks when multiple VMs are cloned from it?  
Kindly provide more details.



  1.  Is there a way to we can mount a QCOW2 image using QCOW2 mounter and have 
a block level view of the data ?  We read about libguestfs but this is 
filesystem view.



  1.  We would like to know when we can expect “Allocation Regions API” . I’m 
referring to

https://bugzilla.redhat.com/show_bug.cgi?id=1622946

This is marked for 4.3 at this point in time.  I presume we will get it as part 
of 4.2.X release as well.

Kindly confirm ?

Thanks
Suchitra


From: pcha...@redhat.com
When: 8:30 PM - 9:00 PM December 13, 2018
Subject: [EXTERNAL] Canceled event: RHV- Veritas Netbackup Weekly Sync @ Thu 
Dec 13, 2018 10am - 10:30am (EST) (suchitra.herwad...@veritas.com)


This event has been canceled.
RHV- Veritas Netbackup Weekly Sync
When

Thu Dec 13, 2018 10am – 10:30am Eastern Time - New York

Calendar

suchitra.herwad...@veritas.com

Who

•

pcha...@redhat.com - organizer

•

mahesh.falm...@veritas.com

•

abhay.mar...@veritas.com

•

nsof...@redhat.com

•

ketan.pachpa...@veritas.com

•

tni...@redhat.com

•

sudhakar.paulzag...@veritas.com

•

suchitra.herwad...@veritas.com

•

navin@veritas.com

•

ehowr...@redhat.com

•

james.ol...@veritas.com

•

adbar...@redhat.com - optional

•

renee.carli...@veritas.com - optional



Agenda:

This Engineering weekly sync will cover the engagement activity for Netbackup 
and RHV integration.




To join the Meeting:


https://bluejeans.com/5723877297


To join via Room System:


Video Conferencing System: 


redhat.bjn.vc
 -or-199.48.152.18


Meeting ID : 5723877297


To join via phone :


1) Dial:


408-915-6466 (United States)


(see all numbers - 


https://www.redhat.com/en/conference-numbers)


2) Enter Conference ID : 5723877297










Invitation from Google Calendar

You are receiving this courtesy email at the account 
suchitra.herwad...@veritas.com because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn 
More.


___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/XA4JPU4D6SF3XWOYONX4J7LIOJP4UBT6/

[ovirt-devel] Re: Announcing 'COVERAGE' option in OST

2018-12-13 Thread Francesco Romani 

On 12/12/18 9:42 PM, Marcin Sobczyk wrote:

Hi,

I've been working on adding coverage report for VDSM in OST
recently, and I'm happy to announce, that the first batch of patches 
is merged!


To run a suite with coverage, look for 'COVERAGE' drop-down on OST's
build parameters page. If you run OST locally, pass a '--coverage' 
argument to 'run_suite.sh'.


Currently, coverage works only for VDSM in basic-suite-master, but adding
VDSM support for other suites is now a no-brainer. More patches are on 
the way!


Since the option is named 'COVERAGE', and not 'VDSM_COVERAGE', other 
projects

are welcome to implement their coverage reports on top of it.

Cheers, Marcin



Kudos!

very nice and very helpful addition.


--
Francesco Romani
Senior SW Eng., Virtualization R
Red Hat
IRC: fromani github: @fromanirh
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/LENCKYBECVR5W3O3SI3YH5SGCFJIJ7OO/

[ovirt-devel] Re: Announcing 'COVERAGE' option in OST

2018-12-13 Thread Sandro Bonazzola 
Thanks Marcin! Yuval, Didi, when you have time can you look if it's easy to
enable coverage for node and otopi related runs using this feature?
Thanks

Il giorno mer 12 dic 2018 alle ore 21:44 Marcin Sobczyk 
ha scritto:

> Hi,
>
> I've been working on adding coverage report for VDSM in OST
> recently, and I'm happy to announce, that the first batch of patches is
> merged!
>
> To run a suite with coverage, look for 'COVERAGE' drop-down on OST's
> build parameters page. If you run OST locally, pass a '--coverage'
> argument to 'run_suite.sh'.
>
> Currently, coverage works only for VDSM in basic-suite-master, but adding
> VDSM support for other suites is now a no-brainer. More patches are on the
> way!
>
> Since the option is named 'COVERAGE', and not 'VDSM_COVERAGE', other
> projects
> are welcome to implement their coverage reports on top of it.
>
> Cheers, Marcin
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-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/devel@ovirt.org/message/UDHD4SQLIGELWYZDBNEDC223DX36L6RT/
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/ROIIPPQGS7SI7IBZFGXZGXULULQ4L3ZM/

[ovirt-devel] Re: Announcing 'COVERAGE' option in OST

2018-12-13 Thread Eyal Edri 
Thanks for submitting it! it's really a great addition to the value OST
gives, it can help prioritize which tests
should be added in the future and also great timing, especially after the
VDSM functional tests on check-merged were removed/pending removal
in favor of running it on OST.

On Wed, Dec 12, 2018 at 10:44 PM Marcin Sobczyk  wrote:

> Hi,
>
> I've been working on adding coverage report for VDSM in OST
> recently, and I'm happy to announce, that the first batch of patches is
> merged!
>
> To run a suite with coverage, look for 'COVERAGE' drop-down on OST's
> build parameters page. If you run OST locally, pass a '--coverage'
> argument to 'run_suite.sh'.
>
> Currently, coverage works only for VDSM in basic-suite-master, but adding
> VDSM support for other suites is now a no-brainer. More patches are on the
> way!
>
> Since the option is named 'COVERAGE', and not 'VDSM_COVERAGE', other
> projects
> are welcome to implement their coverage reports on top of it.
>
> Cheers, Marcin
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-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/devel@ovirt.org/message/UDHD4SQLIGELWYZDBNEDC223DX36L6RT/
>


-- 

Eyal edri


MANAGER

RHV/CNV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/LWRFLFUGPWF7HPEBILHVSJELPE3TGIFF/