[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Milan Zamazal]

Eyal Edri  writes:

> On Mon, Feb 18, 2019 at 4:03 PM Milan Zamazal  wrote:
>
>> Hi, unless there is still anything preventing to make Vdsm 4.3 branch,
>> I'm going to make the branch soon.
>>
>> I posted the following patches to be merged to master soon after the
>> branch is created:
>>
>> - https://gerrit.ovirt.org/97841 (adding ovirt-4.3 to vdsm/stdci.yaml)
>> - https://gerrit.ovirt.org/97842 (adding Vdsm ovirt-4.3 to Jenkins)
>>
>> Once the branch is created:
>>
>> - https://gerrit.ovirt.org/96632 can be merged to master
>>
>> - I'm going to make an ovirt-4.3 patch to redirect oVirt repos in
>>   vdsm/automation from master to 4.3.
>>
>> - OST + Jenkins should be updated to add 4.3 compat suite once Engine
>>   4.3 branch is created too.
>>
>
> Anton, Galit, Dafna - do we have 4.3 suites ready yet?

Let's start with something: https://gerrit.ovirt.org/97926

>> The first patch merged to master after branching 4.3 will be tagged as
>> 4.40.0.
>>
>> Please let me know in case anything more is needed.
>>
>> Thanks,
>> Milan
>> ___
>> 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/HC5UWZER35AR7PF53SQCAALPUAQOZLL3/
>>
___
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/QDT4IHTBLUATXQZG7M2UCBA5WQFMGQRA/

[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Nir Soffer]

On Mon, Feb 18, 2019 at 4:02 PM Milan Zamazal  wrote:

> Hi, unless there is still anything preventing to make Vdsm 4.3 branch,
> I'm going to make the branch soon.
>

We are still working on storage format v5, but we don't want to delay other
work, so we will backport the patches once you branch vdsm.

Current patches in review:
https://gerrit.ovirt.org/q/topic:storage_v5+is:open
https://gerrit.ovirt.org/c/97258/


>
> I posted the following patches to be merged to master soon after the
> branch is created:
>
> - https://gerrit.ovirt.org/97841 (adding ovirt-4.3 to vdsm/stdci.yaml)
> - https://gerrit.ovirt.org/97842 (adding Vdsm ovirt-4.3 to Jenkins)
>
> Once the branch is created:
>
> - https://gerrit.ovirt.org/96632 can be merged to master
>
> - I'm going to make an ovirt-4.3 patch to redirect oVirt repos in
>   vdsm/automation from master to 4.3.
>
> - OST + Jenkins should be updated to add 4.3 compat suite once Engine
>   4.3 branch is created too.
>
> The first patch merged to master after branching 4.3 will be tagged as
> 4.40.0.
>
> Please let me know in case anything more is needed.
>
> Thanks,
> Milan
>
___
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/6MLK7X2IWLQBA6JAELC2BDROQODBDPRZ/

[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Eyal Edri]

On Mon, Feb 18, 2019 at 4:03 PM Milan Zamazal  wrote:

> Hi, unless there is still anything preventing to make Vdsm 4.3 branch,
> I'm going to make the branch soon.
>
> I posted the following patches to be merged to master soon after the
> branch is created:
>
> - https://gerrit.ovirt.org/97841 (adding ovirt-4.3 to vdsm/stdci.yaml)
> - https://gerrit.ovirt.org/97842 (adding Vdsm ovirt-4.3 to Jenkins)
>
> Once the branch is created:
>
> - https://gerrit.ovirt.org/96632 can be merged to master
>
> - I'm going to make an ovirt-4.3 patch to redirect oVirt repos in
>   vdsm/automation from master to 4.3.
>
> - OST + Jenkins should be updated to add 4.3 compat suite once Engine
>   4.3 branch is created too.
>

Anton, Galit, Dafna - do we have 4.3 suites ready yet?


> The first patch merged to master after branching 4.3 will be tagged as
> 4.40.0.
>
> Please let me know in case anything more is needed.
>
> Thanks,
> Milan
> ___
> 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/HC5UWZER35AR7PF53SQCAALPUAQOZLL3/
>


-- 

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/XG6ID5TEIPQRSOONBJWWESGLSIIH4DK7/

[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Milan Zamazal]

Hi, unless there is still anything preventing to make Vdsm 4.3 branch,
I'm going to make the branch soon.

I posted the following patches to be merged to master soon after the
branch is created:

- https://gerrit.ovirt.org/97841 (adding ovirt-4.3 to vdsm/stdci.yaml)
- https://gerrit.ovirt.org/97842 (adding Vdsm ovirt-4.3 to Jenkins)

Once the branch is created:

- https://gerrit.ovirt.org/96632 can be merged to master

- I'm going to make an ovirt-4.3 patch to redirect oVirt repos in
  vdsm/automation from master to 4.3.

- OST + Jenkins should be updated to add 4.3 compat suite once Engine
  4.3 branch is created too.

The first patch merged to master after branching 4.3 will be tagged as
4.40.0.

Please let me know in case anything more is needed.

Thanks,
Milan
___
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/HC5UWZER35AR7PF53SQCAALPUAQOZLL3/

[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Milan Zamazal]

Nir Soffer  writes:

> On Mon, Jan 21, 2019 at 10:30 AM Milan Zamazal  wrote:
>
>> Hi, I'm going to make ovirt-4.3 Vdsm branch next week.
>> If there are any very important reasons not to make it, please let me
>> know.
>>
>
> We have several 4.3 features [1], [2], [3], that require lot of work.
> There is also critical lvm bug [4] that require major changes [5].
>
> Branching too early will make it harder and more risky to have the changes
> in 4.3.
>
> Branching too late add risk from 4.4 work done on master, so we have to
> balance.

There is also problem with ongoing work on Python 3, where it's
difficult to share, synchronize, and not-to-duplicate work by several
people when we can't merge patches.  OTOH the same work could disrupt
finishing and backporting 4.3 patches.

OK, in this case of conflicting interests working hard on the storage
patches looks like the best way to resolve the problem :-).  I'll keep
eye on progress of the work you mention below and let's discuss
branching again in about two weeks.

> [1] incremental backup - https://gerrit.ovirt.org/c/96216/
>  this is only the API, we need to implement them
> [2] 4k support:
> https://gerrit.ovirt.org/q/owner:dchaplyg%2540redhat.com+project:vdsm+is:open
> [3] https://bugzilla.redhat.com/1553133
> [4] https://gerrit.ovirt.org/q/topic:lvm-read-only+is:open
>
> 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/YRKS2RY2GEBQM5XV5MR2INZJKCETGESP/

[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Nir Soffer]

On Mon, Jan 21, 2019 at 10:30 AM Milan Zamazal  wrote:

> Hi, I'm going to make ovirt-4.3 Vdsm branch next week.
> If there are any very important reasons not to make it, please let me
> know.
>

We have several 4.3 features [1], [2], [3], that require lot of work.
There is also critical lvm bug [4] that require major changes [5].

Branching too early will make it harder and more risky to have the changes
in 4.3.

Branching too late add risk from 4.4 work done on master, so we have to
balance.

[1] incremental backup - https://gerrit.ovirt.org/c/96216/
 this is only the API, we need to implement them
[2] 4k support:
https://gerrit.ovirt.org/q/owner:dchaplyg%2540redhat.com+project:vdsm+is:open
[3] https://bugzilla.redhat.com/1553133
[4] https://gerrit.ovirt.org/q/topic:lvm-read-only+is:open

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/ZSLBHOJT3BZNYM3HEOVOSWLJDSXA7Q32/

[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Milan Zamazal]

Sandro Bonazzola  writes:

> Il giorno lun 21 gen 2019 alle ore 09:30 Milan Zamazal 
> ha scritto:
>
>> Hi, I'm going to make ovirt-4.3 Vdsm branch next week.
>> If there are any very important reasons not to make it, please let me
>> know.
>>
>
> Just note we haven't yet finished configuring the 4.3 change queue and the
> 4.3 snapshot repos so once branched 4.3 will become untestable till we
> finish to prepare the 4.3 queue.

OK, thank you for the notice.  I'll check with you about the status
before branching out.

Thanks,
Milan
___
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/YDBVVWFNPOEQ6YPOFHSRVVYLCTLSZMDF/

[ovirt-devel] Re: Vdsm: Intention to make ovirt-4.3 branch

[Sandro Bonazzola]

Il giorno lun 21 gen 2019 alle ore 09:30 Milan Zamazal 
ha scritto:

> Hi, I'm going to make ovirt-4.3 Vdsm branch next week.
> If there are any very important reasons not to make it, please let me
> know.
>

Just note we haven't yet finished configuring the 4.3 change queue and the
4.3 snapshot repos so once branched 4.3 will become untestable till we
finish to prepare the 4.3 queue.



>
> Thanks,
> Milan
> ___
> 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/HESKDGUGL4YN5P4MQVSKDAIFUKPFF7WN/
>


-- 

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/LOCGKPSOZE72RVTQOXFSYTEQZN42SWVH/