Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

2017-01-16 Thread Silvan Kaiser 
For those interested, this is the required local.conf option to switch off
managed snapshot testing:

TEMPEST_VOLUME_MANAGE_SNAPSHOT=False


2017-01-16 10:04 GMT+01:00 Silvan Kaiser :

> Regarding the reason for the failing tests:
> Looks like [1] switches the default for support of managed snapshots to
> true in devstack.
> As the default on that was 'false' until friday Quobyte CI did not set
> that option previously. I'm running tests with a revised config now.
> Btw, feel free to contact me in IRC (kaisers).
> Best
> Silvan
>
> [1] https://review.openstack.org/#/c/419073/
>
>
>
> 2017-01-16 8:52 GMT+01:00 Silvan Kaiser :
>
>> Apoorva, Sean,
>> after some time i managed to bring up Quobyte CI last friday which tested
>> fine [1,2,3] for a short time and then ran into the same issues with 
>> manage_snapshot
>> related tempest tests Apoorva describes (Starting chronologically at [4]).
>> From here i see two steps:
>> a) look into the reason for the issue with manage_snapshot tests
>> b) a short note on how to proceed for marking drivers with reinstated CIs
>> back as supported is much appreciated
>> Best
>> Silvan
>>
>> [1] https://review.openstack.org/#/c/412085/4
>> [2] https://review.openstack.org/#/c/313140/24
>> [3] https://review.openstack.org/#/c/418643/6
>> [4] https://review.openstack.org/#/c/363010/42
>>
>>
>>
>>
>> 2017-01-15 20:46 GMT+01:00 Apoorva Deshpande :
>>
>>> Sean,
>>>
>>> We have resolved issues related to our CI infra[1][2]. At this point
>>> manage_snapshot related tempest tests (2) are failing, but Tintri driver
>>> does not support manage/unmanage snapshot functionalities.
>>>
>>> Could you please assist me on how to skip these tests? We are using
>>> sos-ci for our CI runs.
>>>
>>> If this satisfies the compliance requirements can I propose a patch to
>>> revert changes introduced by [3] and make Tintri driver SUPPORTED again?
>>>
>>> [1] http://openstack-ci.tintri.com/tintri/refs-changes-69-353069-52/
>>> [2] http://openstack-ci.tintri.com/tintri/refs-changes-10-419710-2/
>>> [3] https://review.openstack.org/#/c/411975/
>>>
>>> On Sat, Dec 17, 2016 at 6:34 PM, Apoorva Deshpande 
>>> wrote:
>>>
 Sean,

 As communicated earlier [1][2][3], Tintri CI is facing a devstack
 failure issue, potentially due to [4].
 We are working on it and request you to give us more time before
 approving the unsupported driver patch [5].


 [1] https://www.mail-archive.com/openstack-dev@lists.opensta
 ck.org/msg97085.html
 [2] https://www.mail-archive.com/openstack-dev@lists.opensta
 ck.org/msg97057.html
 [3] http://eavesdrop.openstack.org/irclogs/%23openstack-cind
 er/%23openstack-cinder.2016-12-05.log.html
 [4] https://review.openstack.org/#/c/399550/
 [5] https://review.openstack.org/#/c/411975/

 On Sat, Dec 17, 2016 at 2:05 AM, Sean McGinnis 
 wrote:

> Checking name: Tintri CI
> last seen: 2016-12-16 16:50:50 (0:43:36 old)
> last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old)
> success rate: 19%
>
> Per Cinder's non-compliance policy [1] this patch [2] marks
> the driver as unsupported and deprecated and it will be
> approved if the issue is not corrected by the next cycle.
>
> [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drive
> rs#Non-Compliance_Policy
> [2] https://review.openstack.org/#/c/411975/
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.op
> enstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Dr. Silvan Kaiser
>> Quobyte GmbH
>> Hardenbergplatz 2, 10623 Berlin - Germany
>> +49-30-814 591 800 <+49%2030%20814591800> - www.quobyte.com> uobyte.com/>
>> Amtsgericht Berlin-Charlottenburg, HRB 149012B
>> Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
>>
>
>
>
> --
> Dr. Silvan Kaiser
> Quobyte GmbH
> Hardenbergplatz 2, 10623 Berlin - Germany
> +49-30-814 591 800 <+49%2030%20814591800> - www.quobyte.com quobyte.com/>
> Amtsgericht Berlin-Charlottenburg, HRB 149012B
> Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
>



-- 
Dr. Silvan Kaiser
Quobyte GmbH
Hardenbergplatz 2, 10623 Berlin - Germany
+49-30-814 591 800 - www.quobyte.com
Amtsgericht Berlin-Charlottenburg, HRB 149012B
Management

Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

2017-01-16 Thread GHANSHYAM MANN 
Or how about just disable the flag which will skip snapshot manage tests
for CI where it should not run.

Flag in Devtsack is TEMPEST_VOLUME_MANAGE_SNAPSHOT which can be set to
False on CI.

I added the same on ceph gate jobs [1] and similarly can be added on CI
side if ok?

..1 https://review.openstack.org/#/c/421073/

​-gmann

On Tue, Jan 17, 2017 at 4:32 AM, Sean McGinnis 
wrote:

> On Mon, Jan 16, 2017 at 08:52:34AM +0100, Silvan Kaiser wrote:
> > Apoorva, Sean,
> > after some time i managed to bring up Quobyte CI last friday which tested
> > fine [1,2,3] for a short time and then ran into the same issues with
> > manage_snapshot
> > related tempest tests Apoorva describes (Starting chronologically at
> [4]).
> > From here i see two steps:
> > a) look into the reason for the issue with manage_snapshot tests
> > b) a short note on how to proceed for marking drivers with reinstated CIs
>
> Hey Sylvan,
>
> As mentioned, if the CI requirements can be met yet this cycle, we can
> just do a revert for the patch that set the unsupported flag. That
> should be a quick and easy one to get through once we see the CI is
> back and stable.
>
> Thanks!
> Sean
>
> > back as supported is much appreciated
> > Best
> > Silvan
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

2017-01-16 Thread Sean McGinnis 
On Mon, Jan 16, 2017 at 08:52:34AM +0100, Silvan Kaiser wrote:
> Apoorva, Sean,
> after some time i managed to bring up Quobyte CI last friday which tested
> fine [1,2,3] for a short time and then ran into the same issues with
> manage_snapshot
> related tempest tests Apoorva describes (Starting chronologically at [4]).
> From here i see two steps:
> a) look into the reason for the issue with manage_snapshot tests
> b) a short note on how to proceed for marking drivers with reinstated CIs

Hey Sylvan,

As mentioned, if the CI requirements can be met yet this cycle, we can
just do a revert for the patch that set the unsupported flag. That
should be a quick and easy one to get through once we see the CI is
back and stable.

Thanks!
Sean

> back as supported is much appreciated
> Best
> Silvan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

2017-01-16 Thread Silvan Kaiser 
Regarding the reason for the failing tests:
Looks like [1] switches the default for support of managed snapshots to
true in devstack.
As the default on that was 'false' until friday Quobyte CI did not set that
option previously. I'm running tests with a revised config now.
Btw, feel free to contact me in IRC (kaisers).
Best
Silvan

[1] https://review.openstack.org/#/c/419073/



2017-01-16 8:52 GMT+01:00 Silvan Kaiser :

> Apoorva, Sean,
> after some time i managed to bring up Quobyte CI last friday which tested
> fine [1,2,3] for a short time and then ran into the same issues with 
> manage_snapshot
> related tempest tests Apoorva describes (Starting chronologically at [4]).
> From here i see two steps:
> a) look into the reason for the issue with manage_snapshot tests
> b) a short note on how to proceed for marking drivers with reinstated CIs
> back as supported is much appreciated
> Best
> Silvan
>
> [1] https://review.openstack.org/#/c/412085/4
> [2] https://review.openstack.org/#/c/313140/24
> [3] https://review.openstack.org/#/c/418643/6
> [4] https://review.openstack.org/#/c/363010/42
>
>
>
>
> 2017-01-15 20:46 GMT+01:00 Apoorva Deshpande :
>
>> Sean,
>>
>> We have resolved issues related to our CI infra[1][2]. At this point
>> manage_snapshot related tempest tests (2) are failing, but Tintri driver
>> does not support manage/unmanage snapshot functionalities.
>>
>> Could you please assist me on how to skip these tests? We are using
>> sos-ci for our CI runs.
>>
>> If this satisfies the compliance requirements can I propose a patch to
>> revert changes introduced by [3] and make Tintri driver SUPPORTED again?
>>
>> [1] http://openstack-ci.tintri.com/tintri/refs-changes-69-353069-52/
>> [2] http://openstack-ci.tintri.com/tintri/refs-changes-10-419710-2/
>> [3] https://review.openstack.org/#/c/411975/
>>
>> On Sat, Dec 17, 2016 at 6:34 PM, Apoorva Deshpande 
>> wrote:
>>
>>> Sean,
>>>
>>> As communicated earlier [1][2][3], Tintri CI is facing a devstack
>>> failure issue, potentially due to [4].
>>> We are working on it and request you to give us more time before
>>> approving the unsupported driver patch [5].
>>>
>>>
>>> [1] https://www.mail-archive.com/openstack-dev@lists.opensta
>>> ck.org/msg97085.html
>>> [2] https://www.mail-archive.com/openstack-dev@lists.opensta
>>> ck.org/msg97057.html
>>> [3] http://eavesdrop.openstack.org/irclogs/%23openstack-cind
>>> er/%23openstack-cinder.2016-12-05.log.html
>>> [4] https://review.openstack.org/#/c/399550/
>>> [5] https://review.openstack.org/#/c/411975/
>>>
>>> On Sat, Dec 17, 2016 at 2:05 AM, Sean McGinnis 
>>> wrote:
>>>
 Checking name: Tintri CI
 last seen: 2016-12-16 16:50:50 (0:43:36 old)
 last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old)
 success rate: 19%

 Per Cinder's non-compliance policy [1] this patch [2] marks
 the driver as unsupported and deprecated and it will be
 approved if the issue is not corrected by the next cycle.

 [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drive
 rs#Non-Compliance_Policy
 [2] https://review.openstack.org/#/c/411975/

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Dr. Silvan Kaiser
> Quobyte GmbH
> Hardenbergplatz 2, 10623 Berlin - Germany
> +49-30-814 591 800 <+49%2030%20814591800> - www.quobyte.com quobyte.com/>
> Amtsgericht Berlin-Charlottenburg, HRB 149012B
> Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
>



-- 
Dr. Silvan Kaiser
Quobyte GmbH
Hardenbergplatz 2, 10623 Berlin - Germany
+49-30-814 591 800 - www.quobyte.com
Amtsgericht Berlin-Charlottenburg, HRB 149012B
Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

2017-01-15 Thread Silvan Kaiser 
Apoorva, Sean,
after some time i managed to bring up Quobyte CI last friday which tested
fine [1,2,3] for a short time and then ran into the same issues with
manage_snapshot
related tempest tests Apoorva describes (Starting chronologically at [4]).
>From here i see two steps:
a) look into the reason for the issue with manage_snapshot tests
b) a short note on how to proceed for marking drivers with reinstated CIs
back as supported is much appreciated
Best
Silvan

[1] https://review.openstack.org/#/c/412085/4
[2] https://review.openstack.org/#/c/313140/24
[3] https://review.openstack.org/#/c/418643/6
[4] https://review.openstack.org/#/c/363010/42




2017-01-15 20:46 GMT+01:00 Apoorva Deshpande :

> Sean,
>
> We have resolved issues related to our CI infra[1][2]. At this point
> manage_snapshot related tempest tests (2) are failing, but Tintri driver
> does not support manage/unmanage snapshot functionalities.
>
> Could you please assist me on how to skip these tests? We are using sos-ci
> for our CI runs.
>
> If this satisfies the compliance requirements can I propose a patch to
> revert changes introduced by [3] and make Tintri driver SUPPORTED again?
>
> [1] http://openstack-ci.tintri.com/tintri/refs-changes-69-353069-52/
> [2] http://openstack-ci.tintri.com/tintri/refs-changes-10-419710-2/
> [3] https://review.openstack.org/#/c/411975/
>
> On Sat, Dec 17, 2016 at 6:34 PM, Apoorva Deshpande 
> wrote:
>
>> Sean,
>>
>> As communicated earlier [1][2][3], Tintri CI is facing a devstack failure
>> issue, potentially due to [4].
>> We are working on it and request you to give us more time before
>> approving the unsupported driver patch [5].
>>
>>
>> [1] https://www.mail-archive.com/openstack-dev@lists.opensta
>> ck.org/msg97085.html
>> [2] https://www.mail-archive.com/openstack-dev@lists.opensta
>> ck.org/msg97057.html
>> [3] http://eavesdrop.openstack.org/irclogs/%23openstack-
>> cinder/%23openstack-cinder.2016-12-05.log.html
>> [4] https://review.openstack.org/#/c/399550/
>> [5] https://review.openstack.org/#/c/411975/
>>
>> On Sat, Dec 17, 2016 at 2:05 AM, Sean McGinnis 
>> wrote:
>>
>>> Checking name: Tintri CI
>>> last seen: 2016-12-16 16:50:50 (0:43:36 old)
>>> last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old)
>>> success rate: 19%
>>>
>>> Per Cinder's non-compliance policy [1] this patch [2] marks
>>> the driver as unsupported and deprecated and it will be
>>> approved if the issue is not corrected by the next cycle.
>>>
>>> [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drive
>>> rs#Non-Compliance_Policy
>>> [2] https://review.openstack.org/#/c/411975/
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Dr. Silvan Kaiser
Quobyte GmbH
Hardenbergplatz 2, 10623 Berlin - Germany
+49-30-814 591 800 - www.quobyte.com
Amtsgericht Berlin-Charlottenburg, HRB 149012B
Management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

2017-01-15 Thread Apoorva Deshpande 
Sean,

We have resolved issues related to our CI infra[1][2]. At this point
manage_snapshot related tempest tests (2) are failing, but Tintri driver
does not support manage/unmanage snapshot functionalities.

Could you please assist me on how to skip these tests? We are using sos-ci
for our CI runs.

If this satisfies the compliance requirements can I propose a patch to
revert changes introduced by [3] and make Tintri driver SUPPORTED again?

[1] http://openstack-ci.tintri.com/tintri/refs-changes-69-353069-52/
[2] http://openstack-ci.tintri.com/tintri/refs-changes-10-419710-2/
[3] https://review.openstack.org/#/c/411975/

On Sat, Dec 17, 2016 at 6:34 PM, Apoorva Deshpande 
wrote:

> Sean,
>
> As communicated earlier [1][2][3], Tintri CI is facing a devstack failure
> issue, potentially due to [4].
> We are working on it and request you to give us more time before approving
> the unsupported driver patch [5].
>
>
> [1] https://www.mail-archive.com/openstack-dev@lists.
> openstack.org/msg97085.html
> [2] https://www.mail-archive.com/openstack-dev@lists.
> openstack.org/msg97057.html
> [3] http://eavesdrop.openstack.org/irclogs/%23openstack-cinder/%
> 23openstack-cinder.2016-12-05.log.html
> [4] https://review.openstack.org/#/c/399550/
> [5] https://review.openstack.org/#/c/411975/
>
> On Sat, Dec 17, 2016 at 2:05 AM, Sean McGinnis 
> wrote:
>
>> Checking name: Tintri CI
>> last seen: 2016-12-16 16:50:50 (0:43:36 old)
>> last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old)
>> success rate: 19%
>>
>> Per Cinder's non-compliance policy [1] this patch [2] marks
>> the driver as unsupported and deprecated and it will be
>> approved if the issue is not corrected by the next cycle.
>>
>> [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drive
>> rs#Non-Compliance_Policy
>> [2] https://review.openstack.org/#/c/411975/
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

2016-12-17 Thread Apoorva Deshpande 
Sean,

As communicated earlier [1][2][3], Tintri CI is facing a devstack failure
issue, potentially due to [4].
We are working on it and request you to give us more time before approving
the unsupported driver patch [5].


[1]
https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg97085.html
[2]
https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg97057.html
[3]
http://eavesdrop.openstack.org/irclogs/%23openstack-cinder/%23openstack-cinder.2016-12-05.log.html
[4] https://review.openstack.org/#/c/399550/
[5] https://review.openstack.org/#/c/411975/

On Sat, Dec 17, 2016 at 2:05 AM, Sean McGinnis 
wrote:

> Checking name: Tintri CI
> last seen: 2016-12-16 16:50:50 (0:43:36 old)
> last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old)
> success rate: 19%
>
> Per Cinder's non-compliance policy [1] this patch [2] marks
> the driver as unsupported and deprecated and it will be
> approved if the issue is not corrected by the next cycle.
>
> [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-
> drivers#Non-Compliance_Policy
> [2] https://review.openstack.org/#/c/411975/
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Cinder] Marking Tintri driver as unsupported

2016-12-16 Thread Sean McGinnis 
Checking name: Tintri CI
last seen: 2016-12-16 16:50:50 (0:43:36 old)
last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old)
success rate: 19%

Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if the issue is not corrected by the next cycle.

[1] 
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Non-Compliance_Policy
[2] https://review.openstack.org/#/c/411975/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev