Status update for the last Giant release 0.87.2

Status update for the last Giant release 0.87.2

[Loic Dachary]

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

Hi Abhishek,

Looking at the last two issues marked as needing backport to giant:

http://tracker.ceph.com/projects/ceph/issues?query_id=68

(this link is at the top of http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO) I'm not sure what to do about http://tracker.ceph.com/issues/10643. The problem is that it consistently shows up when testing upgrades that involve giant. We want to be sure Giant can be upgraded to Hammer, therefore we need to keep testing the upgrades at least for a month or two after Hammer is released to catch border cases. I think issue 10643 needs to be fixed and included in 0.87.2 so that we can have clean upgrade tests, otherwise it will mean more work for people watching over the upgrade suites (I mean Yuri here ;-). And wif 10643 is included we can squeeze http://tracker.ceph.com/issues/10153 in as well, I think.

Once this is dealt with and you're done with http://tracker.ceph.com/issues/11259 that you found when running the rgw suite at http://tracker.ceph.com/issues/11153#rgw, 0.87.2 should be good, from our point of view (the point of view of backporters) and we can move to the "asking approval" step of the workflow ( http://tracker.ceph.com/issues/11153#Workflow ). 

What do you think ?

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Status update for the last Giant release 0.87.2

[Abhishek L]

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]


Loic Dachary writes:

> Hi Abhishek,
>
> Looking at the last two issues marked as needing backport to giant:
>
> http://tracker.ceph.com/projects/ceph/issues?query_id=68
>
> (this link is at the top of http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO) I'm not sure what to do about http://tracker.ceph.com/issues/10643. The problem is that it consistently shows up when testing upgrades that involve giant. We want to be sure Giant can be upgraded to Hammer, therefore we need to keep testing the upgrades at least for a month or two after Hammer is released to catch border cases. I think issue 10643 needs to be fixed and included in 0.87.2 so that we can have clean upgrade tests, otherwise it will mean more work for people watching over the upgrade suites (I mean Yuri here ;-). And wif 10643 is included we can squeeze http://tracker.ceph.com/issues/10153 in as well, I think.
>
> Once this is dealt with and you're done with http://tracker.ceph.com/issues/11259 that you found when running the rgw suite at http://tracker.ceph.com/issues/11153#rgw, 0.87.2 should be good, from our point of view (the point of view of backporters) and we can move to the "asking approval" step of the workflow ( http://tracker.ceph.com/issues/11153#Workflow ). 

For this issue, I haven't been able to find out the cause yet, there
seemed to be only one patch that landed in giant related to quotas,
however the test seemed to have failed even before that. I've updated
the tracker with this.
>
> What do you think ?

Overall sounds good. 
-- 
Abhishek

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

Re: Status update for the last Giant release 0.87.2

[Loic Dachary]

[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]


Hi Abhishek,

On 29/03/2015 06:42, Abhishek L wrote:
> 
> Loic Dachary writes:
> 
>> Hi Abhishek,
>>
>> Looking at the last two issues marked as needing backport to giant:
>>
>> http://tracker.ceph.com/projects/ceph/issues?query_id=68
>>
>> (this link is at the top of http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO) I'm not sure what to do about http://tracker.ceph.com/issues/10643. The problem is that it consistently shows up when testing upgrades that involve giant. We want to be sure Giant can be upgraded to Hammer, therefore we need to keep testing the upgrades at least for a month or two after Hammer is released to catch border cases. I think issue 10643 needs to be fixed and included in 0.87.2 so that we can have clean upgrade tests, otherwise it will mean more work for people watching over the upgrade suites (I mean Yuri here ;-). And wif 10643 is included we can squeeze http://tracker.ceph.com/issues/10153 in as well, I think.
>>
>> Once this is dealt with and you're done with http://tracker.ceph.com/issues/11259 that you found when running the rgw suite at http://tracker.ceph.com/issues/11153#rgw, 0.87.2 should be good, from our point of view (the point of view of backporters) and we can move to the "asking approval" step of the workflow ( http://tracker.ceph.com/issues/11153#Workflow ). 
> 
> For this issue, I haven't been able to find out the cause yet, there
> seemed to be only one patch that landed in giant related to quotas,
> however the test seemed to have failed even before that. I've updated
> the tracker with this.

It would be interesting to schedule this test once again to check if it shows up consistently or not (see http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_run_integration_and_upgrade_tests#Re-scheduling-failed-or-dead-jobs-from-an-existing-suite for information about doing that).

>>
>> What do you think ?
> 
> Overall sounds good. 
> 

Cool :-)

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]