Re: [openstack-dev] [cinder] drbdmanage is no more GPL2

Mehdi Abaakouk wrote: > I have recently seen that drbdmanage python library is no more GPL2 but > need a end user license agreement [1]. > Is this compatible with the driver policy of Cinder ? It's not acceptable as a dependency of an OpenStack project (be it GPLv2 or using a custom EULA), see:

Re: [openstack-dev] [cinder] drbdmanage is no more GPL2

On Mon, 2016-12-12 at 07:58 +0100, Mehdi Abaakouk wrote: Hi, I have recently seen that drbdmanage python library is no more GPL2 but need a end user license agreement [1]. Is this compatible with the driver policy of Cinder ? [1]

[openstack-dev] [cinder] drbdmanage is no more GPL2

Hi, I have recently seen that drbdmanage python library is no more GPL2 but need a end user license agreement [1]. Is this compatible with the driver policy of Cinder ? [1] http://git.drbd.org/drbdmanage.git/commitdiff/441dc6a96b0bc6a08d2469fa5a82d97fc08e8ec1 Regards -- Mehdi Abaakouk

Re: [openstack-dev] [cinder] [ceilometer]

On Thu, Dec 08 2016, Jiong Liu wrote: Hi Jeremy, If I'm not mistaken, there's a new pollster in Ocata that uses the Cinder API to get the metrics now, so I think the volume usage audit is getting useless. > Hello Cinder/Ceilometer community, > > > > Is there any guideline on using

[openstack-dev] [cinder] [ceilometer]

Hello Cinder/Ceilometer community, Is there any guideline on using `cinder-volume-usage-audit` command? Search through cinder/ceilometer logs, I find some messages are sent to ceilometer-collector. How do I check the output of this command in ceilometer? Do you have any suggestion?

Re: [openstack-dev] [cinder] consistency groups in ceph

, xing [xing.y...@dell.com] Sent: Tuesday, December 6, 2016 11:07 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Jason Dillaman Subject: Re: [openstack-dev] [cinder] consistency groups in ceph No, the new cloned image (volume) will get this name (volume-uuid) automatically

Re: [openstack-dev] [cinder] consistency groups in ceph

List (not for usage questions) Cc: Jason Dillaman Subject: Re: [openstack-dev] [cinder] consistency groups in ceph Does it mean that ceph as a backend for this feature is supposed to provide an API which allows to specify the name of each cloned image? V. On Tue, Dec 6, 2016 at 7:17 PM, yang, xing

Re: [openstack-dev] [cinder] consistency groups in ceph

not for usage questions) > Cc: Jason Dillaman > Subject: Re: [openstack-dev] [cinder] consistency groups in ceph > > How are the names chosen for those new cloned images? > > On Tue, Dec 6, 2016 at 10:04 AM, yang, xing <xing.y...@dell.com> wrote: &

Re: [openstack-dev] [cinder] consistency groups in ceph

To: OpenStack Development Mailing List (not for usage questions) Cc: Jason Dillaman Subject: Re: [openstack-dev] [cinder] consistency groups in ceph How are the names chosen for those new cloned images? On Tue, Dec 6, 2016 at 10:04 AM, yang, xing <xing.y...@dell.com> wrote: > Hi Victor, >

Re: [openstack-dev] [cinder] consistency groups in ceph

i...@mirantis.com] > Sent: Monday, December 5, 2016 7:13 PM > To: OpenStack Development Mailing List (not for usage questions) > Cc: Jason Dillaman > Subject: Re: [openstack-dev] [cinder] consistency groups in ceph > > I just realized that probably we create images from individual > sn

Re: [openstack-dev] [cinder] consistency groups in ceph

Hi Victor, Yes, you are right. Thanks, Xing From: Victor Denisov [vdeni...@mirantis.com] Sent: Monday, December 5, 2016 7:13 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Jason Dillaman Subject: Re: [openstack-dev] [cinder

Re: [openstack-dev] [cinder] consistency groups in ceph

On Mon, Dec 05, 2016 at 04:13:44PM -0800, Victor Denisov wrote: > I just realized that probably we create images from individual > snapshots of that consistency group and add those images to the new > consistency group. > Am I correct? That is correct.

Re: [openstack-dev] [cinder] consistency groups in ceph

______ >>> From: Victor Denisov [vdeni...@mirantis.com] >>> Sent: Tuesday, November 8, 2016 12:04 AM >>> To: OpenStack Development Mailing List (not for usage questions) >>> Cc: Jason Dillaman >>> Subject: Re: [openstack-dev] [cinder

Re: [openstack-dev] [cinder] consistency groups in ceph

deni...@mirantis.com] >> Sent: Tuesday, November 8, 2016 12:04 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Cc: Jason Dillaman >> Subject: Re: [openstack-dev] [cinder] consistency groups in ceph >> >> One more question. What is the expect

Re: [openstack-dev] [cinder] consistency groups in ceph

tis.com] > Sent: Tuesday, November 8, 2016 12:04 AM > To: OpenStack Development Mailing List (not for usage questions) > Cc: Jason Dillaman > Subject: Re: [openstack-dev] [cinder] consistency groups in ceph > > One more question. What is the expected behavior if you remove a > vol

Re: [openstack-dev] [cinder] [third-party][ci] devstack failures

pps.d...@gmail.com] > *Sent:* Monday, December 5, 2016 7:43 AM > *To:* openstack-dev@lists.openstack.org > *Subject:* [openstack-dev] [cinder] [third-party][ci] devstack failures > > > > Hello, > > > > I am encountering devstack failures on our Cinder CI [1

Re: [openstack-dev] [cinder] [third-party][ci] devstack failures

[mailto:apps.d...@gmail.com] Sent: Monday, December 5, 2016 7:43 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [cinder] [third-party][ci] devstack failures Hello, I am encountering devstack failures on our Cinder CI [1]. Could you please help me debug this? Last successful

Re: [openstack-dev] [cinder] [third-party][ci] devstack failures

On 12/05/2016 04:43 PM, Apoorva Deshpande wrote: > [1] http://openstack-ci.tintri.com/tintri/refs-changes-23-405223-4/ This is failing at 2016-12-05 01:19:17.356 | + functions-common:git_timed:598 : timeout -s SIGINT 0 git clone git://git.openstack.org/openstack/horizon.git

[openstack-dev] [cinder] [third-party][ci] devstack failures

Hello, I am encountering devstack failures on our Cinder CI [1]. Could you please help me debug this? Last successful devstack installation was [2]. [1] http://openstack-ci.tintri.com/tintri/refs-changes-23-405223-4/ [2] http://openstack-ci.tintri.com/tintri/refs-changes-95-393395-7/ thanks,

[openstack-dev] [cinder][oslo] ZeroMQ support with multibackend

Hi, Cinder is lacking ZeroMQ messaging support in multibackend configurations. This is due to the fact that we're abusing ``Target.server`` property by appending "@backend" suffix to the hostname. This works just fine in RabbitMQ, as it routes messages using queue names, but fails in ZeroMQ when

[openstack-dev] [Cinder] Today's meeting cancelled

Hey everyone, Due to flight delays and a very light agenda, today's Cinder meeting is cancelled. Meetings will resume next week. The main thing I wanted to mention today for all cores (and those willing to do the reviews), please try to spend a little time on driver reviews. Our new driver

Re: [openstack-dev] [cinder] consistency groups in ceph

To: OpenStack Development Mailing List (not for usage questions) Cc: Jason Dillaman Subject: Re: [openstack-dev] [cinder] consistency groups in ceph One more question. What is the expected behavior if you remove a volume completely? [Xing] You cannot remove the volume completely (delete volume won't

Re: [openstack-dev] [cinder] consistency groups in ceph

ocs.openstack.org/admin-guide/blockstorage-groups.html > > Thanks, > Xing > > > > From: Victor Denisov [vdeni...@mirantis.com] > Sent: Monday, October 31, 2016 11:29 PM > To: openstack-dev@lists.openstack.org > Cc: Jason Dillaman &g

[openstack-dev] [cinder] generic volume groups and consistency groups

From: yang, xing [xing.y...@dell.com] Sent: Tuesday, November 1, 2016 10:02 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Jason Dillaman Subject: Re: [openstack-dev] [cinder] consistency groups in ceph Hi Victor, Please see my answers inline below. In Newton, we added

[openstack-dev] [cinder][stable] Deprecation notice: Driver for NetApp Data ONTAP operating in 7-mode

Developers and Operators, The NetApp unified driver in Cinder currently provides integration for two major generations of the ONTAP operating system: the current “clustered” ONTAP and the legacy 7-mode. NetApp’s “full support” for 7-mode ended in August of 2015 and the current “limited

[openstack-dev] [Cinder] Ocata Design Summit Recap

The Cinder team had a very productive week at the Design Summit, IMO. There were a lot of great discussions throughout the week, both in Cinder sessions and in the hallways. A huge thank you to all who were able to participate, and a reminder for those that couldn't attend that the PTG is coming

Re: [openstack-dev] [cinder] consistency groups in ceph

...@mirantis.com] Sent: Monday, October 31, 2016 11:29 PM To: openstack-dev@lists.openstack.org Cc: Jason Dillaman Subject: [openstack-dev] [cinder] consistency groups in ceph Hi, I'm working on consistency groups feature in ceph. My question is about what kind of behavior does cinder expect from

[openstack-dev] [cinder] consistency groups in ceph

Hi, I'm working on consistency groups feature in ceph. My question is about what kind of behavior does cinder expect from storage backends. I'm particularly interested in what happens to consistency groups snapshots when I remove an image from the group: Let's imagine I have a consistency group

[openstack-dev] [cinder] [nova] Cinder-Nova API changes weekly meeting cancelled today

Hi, As many of us are either traveling or still jet lagged today we agreed to skip the today’s meeting. The next meeting will be held __ next Monday (November 7) at 1700UTC__. We had progress with the discussions last week and we seem to orient towards a simpler Cinder API, but we still need

Re: [openstack-dev] [Cinder] Proposed logo

On 10/26/2016 03:53 AM, Sean McGinnis wrote: Hey team, Attached is the proposed new logo for the Cinder project. I think some have already seen this, so making sure everyone gets a chance to see it before it's finalized. Sean (smcginnis) FTFY -Ben

Re: [openstack-dev] [Cinder] Proposed logo

Vroom! Looks like a Ferrari in OpenStack Sean McGinnis 于2016年10月26日周三 下午3:55写道： > Hey team, > > Attached is the proposed new logo for the Cinder project. I think some > have already seen this, so making sure everyone gets a chance to see it > before it's finalized. > >

[openstack-dev] [Cinder] Proposed logo

Hey team, Attached is the proposed new logo for the Cinder project. I think some have already seen this, so making sure everyone gets a chance to see it before it's finalized. Sean (smcginnis)__ OpenStack Development

Re: [openstack-dev] [Cinder] No weekly meeting

Cool, wish I could join the next Summit~ Sean McGinnis 于2016年10月19日周三 下午4:57写道： > Hello all, > > I know there are a lot of folks travelling for the Summit already. There > are no agenda items added to the weekly meeting wiki, so I am going to > cancel this weeks meeting. >

[openstack-dev] [Cinder] No weekly meeting

Hello all, I know there are a lot of folks travelling for the Summit already. There are no agenda items added to the weekly meeting wiki, so I am going to cancel this weeks meeting. If there are any important topics or things that need to be discussed prior to the Summit, please bring those up

Re: [openstack-dev] [cinder] How to retrieve volume_driver

this sort of thing in a Barcelona Summit talk [1] showcasing a case where the benefits outweigh the risks. Cheers, Gorka. [1]: https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15159/cinder-always-on-reliability-and-scalability-guide > Użytkownik "Erlon Cruz&

[openstack-dev] [Cinder] Ocata Design Summit schedule

Hey everyone, I've added the Cinder schedule to the list of etherpads with placeholders for each of the sessions. Please feel free to start adding content to them so we have something started. https://wiki.openstack.org/wiki/Design_Summit/Ocata/Etherpads#Cinder Sean (smcginnis)

Re: [openstack-dev] [cinder] How to retrieve volume_driver

On 10/07/2016 12:10 PM, Sean McGinnis wrote: On Fri, Oct 07, 2016 at 05:04:00PM +0200, cr...@interia.pl wrote: Hi Erlon. Thank you for the reply. I need to collect this information to generate sort of overview of drivers used in given environment. Obviously, it potentially is a multiple

Re: [openstack-dev] [cinder] How to retrieve volume_driver

On Fri, Oct 07, 2016 at 05:04:00PM +0200, cr...@interia.pl wrote: > Hi Erlon. > > Thank you for the reply. I need to collect this information to generate sort > of overview of drivers used in given environment. Obviously, it potentially > is a multiple backed one. This information does not

Re: [openstack-dev] [cinder] How to retrieve volume_driver

easy to retrieve). Thanks again and best regards, Lukasz Użytkownik "Erlon Cruz" <sombra...@gmail.com> napisał(a): > Temat: Re: [openstack-dev] [cinder] How to retrieve volume_driver > Data: 2016-10-07 14:19 > Nadawca: "Erlon Cruz" <sombra...@gmail.com>

Re: [openstack-dev] [cinder] How to retrieve volume_driver

Hi Luzasz, This information (volume_driver) is only used on driver loading so, its not available outside Cinder context. Can you tell how and why you need that? And why parsing the conf file is not enough for you? Erlon On Fri, Oct 7, 2016 at 9:05 AM, wrote: > Dear all. > >

[openstack-dev] [cinder] How to retrieve volume_driver

Dear all. I'm a PHD student from Poland and have found out about this list from Openstack wiki. Could you kindly tell me, if there is a way to retrieve, from outside of OpenStack code, volume_driver for given backend? Preferably - without a need to parse the cinder.conf file? It is fairly

Re: [openstack-dev] [cinder][db] lazy loading of an attribute impossible

On 09/30/2016 10:54 AM, Roman Podoliaka wrote: Michał, You are absolutely right: this exception is raised when you try to lazy-load instance attributes outside a Session scope. There is an obvious problem with that - instances do not communicate with a DB on their own - it's left up to

Re: [openstack-dev] [cinder][db] lazy loading of an attribute impossible

Michał, You are absolutely right: this exception is raised when you try to lazy-load instance attributes outside a Session scope. There is an obvious problem with that - instances do not communicate with a DB on their own - it's left up to Session [1]. Unfortunately, it does not play nicely with

Re: [openstack-dev] [cinder] [qa] Proposal to make multinode grenade job voting

+1 It seems good! On Thu, Sep 29, 2016 at 7:25 AM, Michał Dulko wrote: > On 09/29/2016 12:10 PM, Michał Dulko wrote: > > Hello everyone, > > > > We have a non-voting multinode grenade job in check queue for around a > > month now. > > > > https://goo.gl/Kr10s6 > >

Re: [openstack-dev] [cinder] [qa] Proposal to make multinode grenade job voting

On 09/29/2016 12:10 PM, Michał Dulko wrote: > Hello everyone, > > We have a non-voting multinode grenade job in check queue for around a > month now. > > https://goo.gl/Kr10s6 Whoops, I've sent this by mistake. Here's the actual email: Hello everyone, We have a non-voting multinode grenade job

[openstack-dev] [cinder] [qa] Proposal to make multinode grenade job voting

Hello everyone, We have a non-voting multinode grenade job in check queue for around a month now. https://goo.gl/Kr10s6 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Cinder] FFE request for RBD replication

On 12/09, Sean McGinnis wrote: > On Mon, Sep 12, 2016 at 10:24:23AM +0200, Michał Dulko wrote: > > +1, thanks for taking care of that! > > > > On 09/12/2016 03:35 AM, Huang Zhiteng wrote: > > > +1 for this long-waited feature to land in Newton. > > > > > > On Sun, Sep 11, 2016 at 1:09 AM, Jay S.

[openstack-dev] [cinder][db] lazy loading of an attribute impossible

Hi, I've just noticed another Cinder bug [1], similar to past bugs [2], [3]. All of them have a common exception causing them: sqlalchemy.orm.exc.DetachedInstanceError: Parent instance <{$SQLAlchemyObject} at {$MemoryLocation}> is not bound to a Session; lazy load operation of attribute

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On 22 September 2016 at 00:23, John Griffith wrote: > > Yes, that is a sizeable chunk of the solution. The remaining components > are how to coordinate with Nova (compute nodes) and figuring out if we just > use c-vol as is, or if we come up with some form of a paired

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On Wed, Sep 21, 2016 at 12:57 AM, Michał Dulko wrote: > On 09/20/2016 05:48 PM, John Griffith wrote: > > On Tue, Sep 20, 2016 at 9:06 AM, Duncan Thomas > > > wrote: > > > > On 20 September 2016 at 16:24, Nikita

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

Am Mittwoch, den 21.09.2016, 15:49 +0200 schrieb Michał Dulko: > > On 09/21/2016 03:32 PM, Konstanski, Carlos P wrote: > > > > Am Mittwoch, den 21.09.2016, 15:07 +0200 schrieb Michał Dulko: > > > > > > On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote: > > > > > > > > Am Dienstag, den

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

On 09/21/2016 03:32 PM, Konstanski, Carlos P wrote: > Am Mittwoch, den 21.09.2016, 15:07 +0200 schrieb Michał Dulko: >> On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote: >>> Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P: I am currently using python-cinderclient

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

Am Mittwoch, den 21.09.2016, 15:07 +0200 schrieb Michał Dulko: > On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote: > > > > Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P: > > > > > > I am currently using python-cinderclient version 1.5.0, though the code in > > >

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote: > Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P: >> I am currently using python-cinderclient version 1.5.0, though the code in >> question is still in master. >> >> When calling client.services.list() I get this result:

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On 09/20/2016 05:48 PM, John Griffith wrote: > On Tue, Sep 20, 2016 at 9:06 AM, Duncan Thomas > > wrote: > > On 20 September 2016 at 16:24, Nikita Konovalov > > wrote: > >

Re: [openstack-dev] [cinder]tempest test case for force detach volume

) From: Duncan Thomas [duncan.tho...@gmail.com] Sent: 19 September 2016 21:28 To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [cinder]tempest test case for force detach volume Writing a sensible test for this api is rather tricky, since it is intended to clean

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P: > I am currently using python-cinderclient version 1.5.0, though the code in > question is still in master. > > When calling client.services.list() I get this result: "AttributeError: > service" > > The execution path of

[openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

I am currently using python-cinderclient version 1.5.0, though the code in question is still in master. When calling client.services.list() I get this result: "AttributeError: service" The execution path of client.services.list() eventually leads to this method in cinderclient/v2/services.py:24:

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On Tue, Sep 20, 2016 at 9:06 AM, Duncan Thomas wrote: > On 20 September 2016 at 16:24, Nikita Konovalov > wrote: > >> Hi, >> >> From Sahara (and Hadoop workload in general) use-case the reason we used >> BDD was a complete absence of any

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On 20 September 2016 at 16:24, Nikita Konovalov wrote: > Hi, > > From Sahara (and Hadoop workload in general) use-case the reason we used > BDD was a complete absence of any overhead on compute resources > utilization. > > The results show that the LVM+Local target

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

Hi, >From Sahara (and Hadoop workload in general) use-case the reason we used BDD was a complete absence of any overhead on compute resources utilization. The results show that the LVM+Local target perform pretty close to BDD in synthetic tests. It's a good sign for LVM. It actually shows that

Re: [openstack-dev] [cinder] moving driver to open source

Erlon, There are exceptions to this rule ((e.g. libraries used for testing), but the general result of the thread is that all python libraries imported by the drivers must conform to OpenStack licensing. That includes Apache and several other licenses (e.g. MIT, LGPL). Alon On Tue, Sep

Re: [openstack-dev] [cinder] moving driver to open source

On Tue, Sep 20, 2016 at 8:50 AM, Alon Marx wrote: > > From deployment stand point the desire is to have any piece of code that > is required on an openstack installation would be easily downloadable. > And redistributable please. -- *Avishay Traeger, PhD* *System

Re: [openstack-dev] [cinder] moving driver to open source

On Tue, Sep 20, 2016 at 5:23 AM, Thierry Carrez wrote: > Alon Marx wrote: > > Thank you ALL for clearing up this issue. > > > > To sum up the discussion (not going into too many details): > > From legal stand point, if one uses python libraries they should be part > > of

Re: [openstack-dev] [cinder] moving driver to open source

Alon Marx wrote: > Thank you ALL for clearing up this issue. > > To sum up the discussion (not going into too many details): > From legal stand point, if one uses python libraries they should be part > of the community or confirming with the relevant licenses >

Re: [openstack-dev] [cinder] moving driver to open source

Thank you ALL for clearing up this issue. To sum up the discussion (not going into too many details): >From legal stand point, if one uses python libraries they should be part of the community or confirming with the relevant licenses ( http://governance.openstack.org/reference/licensing.html).

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On Mon, Sep 19, 2016 at 2:54 PM, Duncan Thomas wrote: > I think there's some mileage in some further work on adding local LVM, > since things like striping/mirroring for performace can be done. We can > prototype it and get the numbers before even thinking about merging

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

I think there's some mileage in some further work on adding local LVM, since things like striping/mirroring for performace can be done. We can prototype it and get the numbers before even thinking about merging though - as additions to an already fully featured driver. these seem more worthwhile a

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On Mon, Sep 19, 2016 at 12:01 PM, Ivan Kolodyazhny wrote: > + [sahara] because they are primary consumer of the BDD. > > John, > Thanks for the answer. My comments are inline. > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Mon, Sep 19, 2016 at 4:41 PM, John

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

+ [sahara] because they are primary consumer of the BDD. John, Thanks for the answer. My comments are inline. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Sep 19, 2016 at 4:41 PM, John Griffith wrote: > > > On Mon, Sep 19, 2016 at 4:43 AM, Ivan

[openstack-dev] [cinder][nova] API interactions meeting

Hi All, This is a friendly reminder that the next meeting of our series is in less than 50 minutes, at 1700UTC on #openstack-meeting-cp. Thanks and Best Regards, Ildikó __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [cinder]tempest test case for force detach volume

e same time when the features were implemented. > > Best Regards > Chaoyi Huang(joehuang) > > From: Ken'ichi Ohmichi [ken1ohmi...@gmail.com] > Sent: 15 September 2016 2:02 > To: OpenStack Development Mailing List (not for usage questions) &

Re: [openstack-dev] [cinder]tempest test case for force detach volume

; Sent: Saturday, September 17, 2016 8:47:48 PM To: OpenStack Development Mailing List (not for usage questions); shinobu.kj; Shinobu KINJO Subject: Re: [openstack-dev] [cinder]tempest test case for force detach volume Hello, Ken, Thank you for your information, for APIs without tempest test cases, it

[openstack-dev] [cinder] LVM vs BDD drivers performance tests results

Hi team, We did some performance tests [1] for LVM and BDD drivers. All tests were executed on real hardware with OpenStack Mitaka release. Unfortunately, we didn't have enough time to execute all tests and compare results. We used Sahara/Hadoop cluster with TestDFSIO and others tests. All tests

Re: [openstack-dev] [cinder]tempest test case for force detach volume

Regards Chaoyi Huang(joehuang) From: Ken'ichi Ohmichi [ken1ohmi...@gmail.com] Sent: 15 September 2016 2:02 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [cinder]tempest test case for force detach volume Hi Chaoyi

Re: [openstack-dev] [cinder]tempest test case for force detach volume

Hi Chaoyi, That is a nice point. Now Tempest have tests for some volume v2 action APIs which doesn't contain os-force_detach. The available APIs of tempest are two: os-set_image_metadata and os-unset_image_metadata like

[openstack-dev] [cinder] [oslo] privsep socket's client receive thread may crash without attention

Hello everyone: I found an error when backing up a volume with oslo_privsep,it seems that the client channel use a thread to receive socket message,but the thread may crash with inner exception unhandled while the main procedure continues,so I report a bug and upload a patchset to fix:

[openstack-dev] [cinder]tempest test case for force detach volume

Hello, Is there ant tempest test case for "os-force_detach" action to force detach a volume? I didn't find such a test case both in the repository https://github.com/openstack/cinder/tree/master/cinder/tests/tempest and https://github.com/openstack/tempest The API link is:

Re: [openstack-dev] [Cinder] FFE request for RBD replication

+1 Since this is very isolated to the rbd driver and it's passing already Walt On 09/09/2016 12:32 PM, Gorka Eguileor wrote: Hi, As some of you may know, Jon Bernard (jbernard on IRC) has been working on the RBD v2.1 replication implementation [1] for a while, and we would like to request a

Re: [openstack-dev] [cinder] moving driver to open source

On 13 September 2016 at 06:44, Ben Swartzlander wrote: > On 09/09/2016 11:12 AM, Duncan Thomas wrote: > >> I don't care so much whether your CLI or API proxy in open or closed >> source, but I really do care if I can create a distribution, even a >> novel one, with that

Re: [openstack-dev] [cinder] moving driver to open source

On 2016-09-12 23:44:10 -0400 (-0400), Ben Swartzlander wrote: [...] > I don't understand how you can have this stance while tolerating the > existence of such things as the VMware driver. That software (ESXi) > absolutely requires a license to use or distribute. If it has to be installed on the

Re: [openstack-dev] [cinder] moving driver to open source

On 09/09/2016 11:12 AM, Duncan Thomas wrote: On 9 September 2016 at 17:22, Ben Swartzlander > wrote: On 09/08/2016 04:41 PM, Duncan Thomas wrote: Despite the fact I've appeared to be slightly disagreeing with John in

Re: [openstack-dev] [Cinder] FFE request for RBD replication

Thanks everyone for the quick and positive responses. I'm on PTO this week with limited internet access, so my replies may have some delays. Next week it will go back to normal. :-) Cheers, Gorka. On Mon, Sep 12, 2016 at 3:04 PM, Sean McGinnis wrote: > On Mon, Sep 12,

Re: [openstack-dev] [Cinder] PTL candidacy

+1. Sean's services as Cinder PTL is really appreciable!! Regards, Sheel Rana On Sep 12, 2016 7:11 PM, "Sean McGinnis" wrote: Hello everyone, I would like to announce my candidacy to continue as Cinder PTL for the Ocata release. The Cinder project has made great

[openstack-dev] [Cinder] PTL candidacy

Hello everyone, I would like to announce my candidacy to continue as Cinder PTL for the Ocata release.

Re: [openstack-dev] [Cinder] FFE request for RBD replication

On Mon, Sep 12, 2016 at 10:24:23AM +0200, Michał Dulko wrote: > +1, thanks for taking care of that! > > On 09/12/2016 03:35 AM, Huang Zhiteng wrote: > > +1 for this long-waited feature to land in Newton. > > > > On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant > >

Re: [openstack-dev] [Cinder] FFE request for RBD replication

+1, thanks for taking care of that! On 09/12/2016 03:35 AM, Huang Zhiteng wrote: > +1 for this long-waited feature to land in Newton. > > On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant > > > wrote: > > +1 from me. It is

Re: [openstack-dev] [Cinder] FFE request for RBD replication

+1 for this long-waited feature to land in Newton. On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant < jsbry...@electronicjungle.net> wrote: > +1 from me. It is making good progress and is low risk. > > -Jay > > > > On 09/09/2016 02:32 PM, Gorka Eguileor wrote: > >> Hi, >> >> As some of you may

Re: [openstack-dev] [cinder] moving driver to open source

On Sep 9, 2016 18:13, "Duncan Thomas" > So my issue is not with any of those things, it is that I believe anybody should be able to put together a distribution of openstack, that just works, which any supported backend, without needed to negotiate licensing deals with vendors, and without having

Re: [openstack-dev] [Cinder] FFE request for RBD replication

+1 from me. It is making good progress and is low risk. -Jay On 09/09/2016 02:32 PM, Gorka Eguileor wrote: Hi, As some of you may know, Jon Bernard (jbernard on IRC) has been working on the RBD v2.1 replication implementation [1] for a while, and we would like to request a Feature Freeze

Re: [openstack-dev] [Cinder] FFE request for RBD replication

Given the the patch is up and well on its way I don't know why this would be a problem. FWIW ya get my +1 On Sep 9, 2016 1:34 PM, "Gorka Eguileor" wrote: > Hi, > > As some of you may know, Jon Bernard (jbernard on IRC) has been working > on the RBD v2.1 replication

[openstack-dev] [Cinder] FFE request for RBD replication

Hi, As some of you may know, Jon Bernard (jbernard on IRC) has been working on the RBD v2.1 replication implementation [1] for a while, and we would like to request a Feature Freeze Exception for that work, as we believe it is a good candidate being a low risk change for the integrity of the

Re: [openstack-dev] [cinder] moving driver to open source

On Sep 9, 2016 08:26, "Ben Swartzlander" wrote: > > On 09/08/2016 04:41 PM, Duncan Thomas wrote: >> >> On 8 September 2016 at 20:17, John Griffith > > wrote: >> >> On Thu, Sep 8, 2016 at 11:04 AM, Jeremy

Re: [openstack-dev] [cinder] moving driver to open source

On 9 September 2016 at 17:22, Ben Swartzlander wrote: On 09/08/2016 04:41 PM, Duncan Thomas wrote: > > Despite the fact I've appeared to be slightly disagreeing with John in >> the IRC discussion on this subject, you've summarised my concern very >> well. I'm not

Re: [openstack-dev] [cinder] moving driver to open source

On 09/08/2016 04:41 PM, Duncan Thomas wrote: On 8 September 2016 at 20:17, John Griffith > wrote: On Thu, Sep 8, 2016 at 11:04 AM, Jeremy Stanley > wrote: they

Re: [openstack-dev] [cinder] moving driver to open source

On 2016-09-08 23:41:42 +0300 (+0300), Duncan Thomas wrote: > Despite the fact I've appeared to be slightly disagreeing with John in the > IRC discussion on this subject, you've summarised my concern very well. I'm > not convinced that these support tools need to be open source, but they >

Re: [openstack-dev] [cinder] moving driver to open source

On 8 September 2016 at 20:17, John Griffith wrote: > On Thu, Sep 8, 2016 at 11:04 AM, Jeremy Stanley wrote: > > > > they should be able to simply install it and its free dependencies >> and get a working system that can communicate with

Re: [openstack-dev] [cinder] moving driver to open source

On Thu, Sep 8, 2016 at 11:04 AM, Jeremy Stanley wrote: > On 2016-09-08 09:32:20 +0100 (+0100), Daniel P. Berrange wrote: > > That policy is referring to libraries (ie, python modules that we'd > > actually "import" at the python level), while the list above seems to be > >

Re: [openstack-dev] [cinder] moving driver to open source

On 2016-09-08 09:32:20 +0100 (+0100), Daniel P. Berrange wrote: > That policy is referring to libraries (ie, python modules that we'd > actually "import" at the python level), while the list above seems to be > referring to external command line tools that we merely invoke from the > python code.

Re: [openstack-dev] [cinder] moving driver to open source

On Thu, Sep 8, 2016 at 2:32 AM, Daniel P. Berrange wrote: > On Thu, Sep 08, 2016 at 10:24:09AM +0200, Thierry Carrez wrote: > > Avishay Traeger wrote: > > > There are a number of drivers that require closed-source tools to > > > communicate with the storage. 3 others that

<    1   2   3   4   5   6   7   8   9   10   >