Re: [openstack-dev] [Cinder] about policy.json in unit test

On 02:04 Tue 29 Apr , Bohai (ricky) wrote: > Hi stackers, > > I found there are two "policy.json" files in cinder project. > One is for source code(cinder/etc/policy.json), another is for the unit > test(cinder/cinder/tests/policy.json). > > Maybe it's better to united them and make the unit

Re: [openstack-dev] [Cinder] Qcow2 support for cinder-backup

On 12:45 Mon 12 May , Zhangleiqiang (Trump) wrote: > Hi, all: > > I have planned to add the support to create qcow2 format file in NFS > driver ([1]). From the comment of Eric Harney, I know that cinder-backup > service currently assumes the volume is raw-formatted, and enable creating

Re: [openstack-dev] [Cinder] Qcow2 support for cinder-backup

Hi, I did a design session on Friday though my proposal was to capture the delta as qcow2. Here is the link to ether pad notes. https://etherpad.openstack.org/p/juno-cinder-changed-block-list Do you see synergies between what you are proposing and my proposal? Shouldn¹t we standardize on one for

Re: [openstack-dev] [Cinder] about policy.json in unit test

On Mon, May 19, 2014 at 1:14 AM, Mike Perez wrote: > On 02:04 Tue 29 Apr , Bohai (ricky) wrote: > > Hi stackers, > > > > I found there are two "policy.json" files in cinder project. > > One is for source code(cinder/etc/policy.json), another is for the unit > test(cinder/cinder/tests/policy.j

Re: [openstack-dev] [Cinder] about policy.json in unit test

: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] about policy.json in unit test On Mon, May 19, 2014 at 1:14 AM, Mike Perez mailto:thin...@gmail.com>> wrote: On 02:04 Tue 29 Apr , Bohai (ricky) wrote: > Hi stackers, > > I foun

Re: [openstack-dev] [Cinder] about policy.json in unit test

) *Subject:* Re: [openstack-dev] [Cinder] about policy.json in unit test On Mon, May 19, 2014 at 1:14 AM, Mike Perez <mailto:thin...@gmail.com>> wrote: On 02:04 Tue 29 Apr , Bohai (ricky) wrote: > Hi stackers, > > I found there are two "policy.json" files in cinder pr

Re: [openstack-dev] [Cinder] Qcow2 support for cinder-backup

On 18 May 2014 12:32, Murali Balcha wrote: > Hi, > I did a design session on Friday though my proposal was to capture the > delta as qcow2. Here is the link to ether pad notes. > > https://etherpad.openstack.org/p/juno-cinder-changed-block-list > > > Do you see synergies between what you are propo

Re: [openstack-dev] [Cinder] Qcow2 support for cinder-backup

ge- > From: Duncan Thomas [mailto:duncan.tho...@gmail.com] > Sent: Wednesday, May 28, 2014 9:41 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Cinder] Qcow2 support for cinder-backup > > On 18 May 2014 12:32, Murali Balcha wrote: > &g

Re: [openstack-dev] [Cinder] DRBD integration as volume driver

The best thing to do with the code is push up a gerrit review! No need to be shy, and you're very welcome to push up code before the blueprint is in, it just won't get merged. I'm very interested in this code. On 3 June 2014 09:06, Philipp Marek wrote: > Hi everybody, > > at the Juno Design Summ

Re: [openstack-dev] [Cinder] DRBD integration as volume driver

Hello Duncan, > The best thing to do with the code is push up a gerrit review! No need > to be shy, and you're very welcome to push up code before the > blueprint is in, it just won't get merged. thank you for your encouragement! I pushed another fix for Cinder last week (2 lines, allowing to st

Re: [openstack-dev] [Cinder] DRBD integration as volume driver

So, I now tried to push the proof-of-concept driver to Gerrit, and got this: > Downloading/unpacking dbus (from -r /home/jenkins/workspace/gate- cinder-pep8/requirements.txt (line 32)) > http://pypi.openstack.org/openstack/dbus/ uses an insecure transport scheme (http). Consider using https if

Re: [openstack-dev] [Cinder] DRBD integration as volume driver

Hrmpf, sent too fast again. I guess https://wiki.openstack.org/wiki/Requirements is the link I was looking for. Sorry for the noise. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/

[openstack-dev] [cinder] Not seeking another term as PTL

Hey Everyone, I've been kinda mixed on this one, but I think it's a good time for me to not run for Cinder PTL. I've been filling the role since we started the idea back at the Folsom Summit, and it's been an absolute pleasure and honor for me. I don't plan on going anywhere and will still be in

[openstack-dev] [cinder] Any plan on cinder for kilo?

Hi, I noticed nova has already opened blueprint and specs for kilo, so I was wondering what is the plan on cinder for kilo? If I want to contribute some code(add new feature) for cinder, whether the step is the same with nova (need write specs first)? Thanks! Yoo __

Re: [openstack-dev] [cinder] Adding support for iSCSI helper

On Wed, Nov 5, 2014 at 12:40 AM, Anish Bhatt wrote: > Do the minimum driver features listed here > https://wiki.openstack.org/wiki/Cinder#Minimum_Driver_Features still hold > if I’m trying to add support for something that is a drop in replacement for > iet/tgt that has no volume support. Does th

Re: [openstack-dev] [cinder] Adding support for iSCSI helper

ct: Re: [openstack-dev] [cinder] Adding support for iSCSI helper > > On Wed, Nov 5, 2014 at 12:40 AM, Anish Bhatt wrote: > > Do the minimum driver features listed here > > https://wiki.openstack.org/wiki/Cinder#Minimum_Driver_Features still > > hold if I’m trying to a

[openstack-dev] [cinder]How to do the cert test?

I have read the related article in https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers, but I still have a little confused about the cert test: 1. Should I run the the tempest (at https://github.com/openstack/tempest) in our own 3rd party CI test environment? Our 3rd party CI have a

Re: [openstack-dev] [cinder] Adding support for iSCSI helper

On 01:35 Wed 05 Nov , Anish Bhatt wrote: > This is very helpful, thank you ! Is this planned for kilo ? Yes. -- Mike Perez ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openst

[openstack-dev] [Cinder][DR]replication/CG support in driver

Hi all, We want to add replication/CG related support in huawei driver, would this also be bound to the Dec.19th deadline? There is confusion on whether the deadline is for new drivers or for all the proposals for Kilo. As I remembered in the design summit meetup, it was set for the new drivers co

Re: [openstack-dev] [Cinder] mid-cycle meet-up planning ...

Jay S. Bryant wrote: > For those of you that weren't able to make the Kilo meet-up in Paris I > wanted to send out a note regarding Cinder's Kilo mid-cycle meet-up. > > IBM has offered to host it in, warm, sunny, Austin, Texas. The planned > dates are January 27, 28 and 29, 2015. > > I have put

[openstack-dev] [Cinder] Mid-cycle meetup for Cinder devs

During the June 11 #openstack-cinder meeting we discussed a mid-cycle meetup. The agenda is To be Determined. I have inquired and HP in Fort Collins, CO has room and network connectivity available. There were some dates that worked well for reserving a nice room: July 14,15,17,18, 21-25, 27-Aug 1

Re: [openstack-dev] [cinder] Minimum Driver Features for juno

I'm pretty sure they haven't changed from Icehouse, see https://github.com/openstack/cinder/blob/master/doc/source/devref/drivers.rst On 20 June 2014 12:49, Yogesh Prasad wrote: > Hi All, > > Please tell me what are the minimum Driver Features for juno release. > > -- > Thanks & Regards, > Yoge

[openstack-dev] [cinder][glance] Update volume-image-metadata proposal

Hi folks, I started working on this blueprint [1] but the work to be done is not limited to cinder python client. Volume-image-metadata is immutable in Cinder and Glance has RBAC image properties and it doesn't provide any way to find out which are those protecte

Re: [openstack-dev] [cinder][volume/manager.py] volume driver mapping

That's easy; you don't. The mappings are their because we moved some drivers round during a code cleanup and didn't want old config files to break during an upgrade. The old names have been deprecated since Falsom and finally now removed; new drivers don't need to do any mapping at all. On 25 June

Re: [openstack-dev] [cinder][volume/manager.py] volume driver mapping

This seems cool. Does it mean the storage vendors write their new drivers & just map it from cinder.conf ? Does it involve any changes to devstack as well ? Regards, Amit *CloudByte Inc.* On Wed, Jun 25, 2014 at 7:22 PM, Duncan Thomas wrote: > That's easy; you don

Re: [openstack-dev] [cinder][volume/manager.py] volume driver mapping

On 26 June 2014 05:46, Amit Das wrote: > This seems cool. > > Does it mean the storage vendors write their new drivers & just map it from > cinder.conf ? Correct. You can cause devstack to set up cinder.conf for you by setting CINDER_DRIVER=cinder.volume.drivers.foo.bar in local.conf before you s

[openstack-dev] [cinder][replication-api] replication_rpo_range - why two values?

"replication_rpo_range" currently gets set with two values - a lower and an upper bound. File cinder/scheduler/filter_scheduler.py:118 has if target_rpo < rpo_range[0] or target_rpo > rpo_range[1]: Why do we check for "target_rpo > rpo_range[1]"? "Don't use that one if replication is too fas

Re: [openstack-dev] [cinder][replication-api] extra_specs too constant

of course impact the actual RPO, but I think this is outside the scope of this 1st revision - I would like to see this mechanism enhanced in the next revision. Ronen, From: Philipp Marek To: openstack-dev@lists.openstack.org, Cc: Ronen Kat/Haifa/IBM@IBMIL Date: 11/07/2014 04

Re: [openstack-dev] [cinder][nova] cinder querying nova-api

So I see a couple of issues here: 1) reliability - need to decide what the scheduler does if the nova api isn't responding - hanging and ignoring future scheduling requests is not a good option... a timeout and putting the volume into error might be fine. 2) Nova doesn't expose hostname as identi

Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question

I think, It should be on the cinder node which is usually deployed on the controller node From: Johnson Cheng [mailto:johnson.ch...@qsantechnology.com] Sent: Thursday, July 17, 2014 10:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Cinder

Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question

List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question I think, It should be on the cinder node which is usually deployed on the controller node From: Johnson Cheng [mailto:johnson.ch...@qsantechnology.com] Sent: Thursday, July 17, 2014 10:38

Re: [openstack-dev] [cinder][nova] cinder querying nova-api

Thanks Thomas, What I'm trying to achieve is the following : To be able to create a VM on a host (that's a compute and volume host at the same time) then call cinder and let it find the host and create and attach volumes there. I guess the biggest problem is to be able to identify the host, a

Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question

(not for usage questions) Subject: Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question I think, It should be on the cinder node which is usually deployed on the controller node From: Johnson Cheng [mailto:johnson.ch...@qsantechnology.com] Sent: Thursday, July 17, 2014 10:38 AM To:

Re: [openstack-dev] [cinder][nova] cinder querying nova-api

On 17 July 2014 08:36, Abbass MAROUNI wrote: > Thanks Thomas, > > What I'm trying to achieve is the following : > To be able to create a VM on a host (that's a compute and volume host at the > same time) then call cinder and let it find the host and create and attach > volumes there. > > I guess t

Re: [openstack-dev] [cinder][nova] cinder querying nova-api

Abbass, There has been discussion around this in the past. As it would be a significant feature you should open a spec for it. Do a 'git clone https://github.com/openstack/cinder-specs. There are directions in there for actually submitting the spec. Thanks! Jay On Fri, 2014-07-18 at 09:01 +02

Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question

y it seems not attach to a iSCSI LUN automatically because I can > not discover it from iSCSI initiator, > > #> iscsiadm -m discovery -t st -p 192.168.106.20 > > > > Do I miss something? > > > > > > Regards, > > Johnson > > > > > > F

Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question

PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question The iSCSI lun won't be set up until you try to attach the volume On 17 July 2014 12:44, Johnson Cheng wrote: > Dear All, > > > > I in

Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question

> -Original Message- > From: Duncan Thomas [mailto:duncan.tho...@gmail.com] > Sent: Monday, July 21, 2014 6:16 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question > > The iSCSI lun won&#x

Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question

t [mailto:jsbry...@electronicjungle.net] Sent: Monday, July 21, 2014 11:53 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question Johnson, I am not sure what you mean by 'attach volume manually'. Do you mean wh

[openstack-dev] [cinder][qa] cinder client versions and tempest

I noticed that the cinder list-extensions url suffix is underneath the v1/v2 in the GET url but the returned result is the same either way. Some of the returned items have v1 in the namespace, and others v2. Also, in tempest, there is a single config section for cinder and only a single extens

[openstack-dev] [Cinder] Volume replication - driver support walk through

Hello, The initial code for managing volume replication in Cinder is now available as work-in-progress - see https://review.openstack.org/#/c/106718 I expect to remove the work-in-progress early next week. I would like to hold a walk through of the replication feature for Cinder driver owners

Re: [openstack-dev] Cinder tempest api volume tests failed

On 11:30 Thu 31 Jul , Nikesh Kumar Mahalka wrote: > I deployed a single node devstack on Ubuntu 14.04. > This devstack belongs to Juno. > > When i am running tempest api volume test, i am getting some tests failed. Hi Nikesh, To further figure out what's wrong, take a look at the c-vol, c-ap

[openstack-dev] [OpenStack-Dev] Cinder API Web Framework Change

All, I wanted to loop the larger community in on some discussions that have been taking place on #openstack-cinder. During the Summit we talked about switching to Pecan for our API/Web framework. Since then we've registered a BP [1] and some pretty good progress has been made. Since starting th

Re: [openstack-dev] [cinder][conductor] Creating a new service

On 06/27/2013 02:56 AM, Nikolay Starodubtsev wrote: > Hi, everyone! In the begining of June I create a blueprint about > cinder-conductor. Can anyone take a look at it? > Here it is: https://blueprints.launchpad.net/cinder/+spec/no-db-volume It's not immediately obvious why it's a problem for cind

Re: [openstack-dev] [cinder][conductor] Creating a new service

On Thu, Jun 27, 2013 at 9:56 AM, John Griffith wrote: > > > > On Thu, Jun 27, 2013 at 9:47 AM, Russell Bryant wrote: > >> On 06/27/2013 02:56 AM, Nikolay Starodubtsev wrote: >> > Hi, everyone! In the begining of June I create a blueprint about >> > cinder-conductor. Can anyone take a look at it? >

Re: [openstack-dev] [cinder][conductor] Creating a new service

On Thu, Jun 27, 2013 at 9:47 AM, Russell Bryant wrote: > On 06/27/2013 02:56 AM, Nikolay Starodubtsev wrote: > > Hi, everyone! In the begining of June I create a blueprint about > > cinder-conductor. Can anyone take a look at it? > > Here it is: https://blueprints.launchpad.net/cinder/+spec/no-db

Re: [openstack-dev] [cinder] A friendly reminder about reviews

Cinder is definitely lacking reviewing force. I remember 2 years ago comparing with today and I can tell that patches are taking a lot longer to get reviewed. This link is also very useful to triage incoming patches: https://review.openstack.org/#/dashboard/?foreach=project:^openstack/.*cinder.*

[openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

I would like to nominate Scott D'Angelo to core. Scott has been very involved in the project for a long time now and is always ready to help folks out on IRC. His contributions [1] have been very valuable and he is a thorough reviewer [2]. Please let me know if there are any objects to this within

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cindercore

ates From: Eric Harney To: openstack-dev@lists.openstack.org Date: 06/28/2016 10:07 AM Subject:Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core On 06/27/2016 01:27 PM, Sean McGinnis wrote:

[openstack-dev] [Cinder][Nova] Scheduling issue for the Summit

Unfortunately I am way late at noticing this, but bringing it up in case there's anything that can still be done about it. Tuesday the 9th, from 11:15am-11:55am, is going to be a challenge for me. The Track Chairs Recap, Using Cinder for Nova Ephemeral Storage, and the Cinder - Project Onboarding

[openstack-dev] [cinder] About cinder-volume HA A/A

Hello, cinder developers. What progress about cinder-volume HA A/A? In the release notes[1], cinder-volume HA A/A is still progress from Newton to Ocata and there is so many patches and progress on the feature page[2], but it doesn't look like up-to-date, It's difficult to understand the current s

Re: [openstack-dev] [Cinder] Not not running for PTL

Sean, Thank you for all your hard work! It was a great 4 cycles. I hope, after you take some rest you'll be elected for PTL later. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Fri, Jul 21, 2017 at 2:05 PM, Sean McGinnis wrote: > Hey everyone, > > So this isn't an "I'm stepping down at

Re: [openstack-dev] [Cinder] Not not running for PTL

Thanks Ivan! :) On Tue, Jul 25, 2017 at 10:42:55AM +0300, Ivan Kolodyazhny wrote: > Sean, > > Thank you for all your hard work! It was a great 4 cycles. I hope, after > you take some rest you'll be elected for PTL later. > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Fri, Jul

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

+1 On Tue, Jul 25, 2017 at 1:07 AM, Sean McGinnis wrote: > I am proposing we add TommyLike as a Cinder core. > > DISCLAIMER: We work for the same company. > > I have held back on proposing him for some time because of this conflict. > But > I think from his number of reviews [1] and code contrib

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

Core team, I will also note that I mentioned this to Sean back around the time of the Boston Summit, before he mentioned it to me. I had asked a few other team members and decided I would wait a little longer to ensure the numbers were consistent before making the proposal. So, Sean just be

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

On 07/25/2017 04:07 AM, Sean McGinnis wrote: > I am proposing we add TommyLike as a Cinder core. > > DISCLAIMER: We work for the same company. > > I have held back on proposing him for some time because of this conflict. But > I think from his number of reviews [1] and code contributions [2] it's

Re: [openstack-dev] [Cinder] Pike feature work wrap up

Sean, Thanks for getting the list put together and updated. Backup Driver Init has merged. I merged Backup Metadata. Do we have more info on the the Extend Attached Volume client change? Jay On 7/25/2017 2:55 AM, Sean McGinnis wrote: Hey team, This Thursday is feature freeze, and we still

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

+1, Tommy did a good job contributing both in reviews and code Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 25, 2017 at 7:21 PM, Tom Barron wrote: > On 07/25/2017 04:07 AM, Sean McGinnis wrote: > > I am proposing we add TommyLike as a Cinder core. > > > > DISCLAIMER: We work f

Re: [openstack-dev] [Cinder] Not not running for PTL

Hi, Sean It's very nice to work together with you in Cinder team, I just want to thank you for your hard work in those cycles. I have been there for 4 years, fortunately we have very great PTLs and Cores to help our new guys to grow up. No matter if you are PTL in next cycle, it's both very hap

[openstack-dev] [Cinder] Requirements for re-adding Gluster support

Hello, In one of the last Cinder releases support for Gluster has been dropped. The commit message [1] mentions that the support has been marked deprecated during Newton. It seems that there are quite some users in the Gluster Community that run OpenStack with Gluster storage. These users did not

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

+1! Tommy is great addition to Cinder core team. Thanks, Xing From: Sean McGinnis [sean.mcgin...@gmx.com] Sent: Tuesday, July 25, 2017 4:07 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

17 4:07 AM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core > > I am proposing we add TommyLike as a Cinder core. > > DISCLAIMER: We work for the same company. > > I have held back on proposing him for some time because of thi

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

+1 -Patrick On Tue, Jul 25, 2017 at 1:07 AM, Sean McGinnis wrote: > I am proposing we add TommyLike as a Cinder core. > > DISCLAIMER: We work for the same company. > > I have held back on proposing him for some time because of this conflict. > But > I think from his number of reviews [1] and co

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

On 03:07 Jul 25, Sean McGinnis wrote: > I am proposing we add TommyLike as a Cinder core. > > DISCLAIMER: We work for the same company. > > I have held back on proposing him for some time because of this conflict. But > I think from his number of reviews [1] and code contributions [2] it's > hope

Re: [openstack-dev] [Cinder] Not not running for PTL

Sean, Thank you for all you have done for the project over the last 4 cycles. Anyone who may step up to take your place will have big shoes to fill! Jay On 7/21/2017 6:05 AM, Sean McGinnis wrote: Hey everyone, So this isn't an "I'm stepping down at the end of this cycle" message, but it i

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

I'm a little late getting back to it, but I have just added TommyLike to the Gerrit and Launchpad groups. Welcome to the Cinder core team TommyLike. We're glad to have you. Sean On Tue, Jul 25, 2017 at 03:07:08AM -0500, Sean McGinnis wrote: > I am proposing we add TommyLike as a Cinder core. >

Re: [openstack-dev] [Cinder] Proposing TommyLikeHu for Cinder core

Thank you Sean and Cinder team. It's my honor to be a member of the big family, looking forward to work with all of you! Sean McGinnis 于2017年8月3日周四 上午9:21写道： > I'm a little late getting back to it, but I have just added TommyLike > to the Gerrit and Launchpad groups. > > Welcome to the Cinder co

[openstack-dev] [Cinder] string freeze exception for VMAX driver

To whom it may concern, I would like to request a string freeze exception for 2 patches that are on the merge queue for Pike. 1. VMAX driver - align VMAX QOS settings with front end (CI Passed) https://review.openstack.org/#/c/484885/7/cinder/volume/drivers/dell_emc/vmax/rest.py line 8

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

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.open

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

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 snapsho

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

Hi Sean, please review these commits in drbdmanage upstream: http://git.drbd.org/drbdmanage.git/commit/2312d7e7657f98728b6ae1601d8c77010f6adca2 http://git.drbd.org/drbdmanage.git/commit/24ff36ec21f5b7cfdfe38b1888b64eb01f463240 Basically everything behind the dbus API GPL-v3. All files included by

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

Hi All, Unfortunately our current meeting slot (every Monday 1700UTC) is in collision for several of the regular attendees. In an attempt to find a new slot I checked the available meeting channels for the same time slot over the week and we have at least on available currently for each day. S

Re: [openstack-dev] [cinder] Cinder with remote LVM proposal

Hi Marco, What you are proposing is almost like to create an LVM storage box. I haven't seen any real benefit from the advantages you listed. For 1), the same problems you can have upgrading the services within the same node will happen if the LVM services are not in the same host. For, 2), now yo

Re: [openstack-dev] [cinder] Cinder with remote LVM proposal

Hi everybody, > > Hi, I'd like to know if it is possible to use openstack-cinder-volume with > > a remote LVM. This could be a new feature proposal if the idea is good. > > More precisely, I'm thinking a solution where openstack-cinder-volume runs > > on a dedicated node and LVM on another node (c

Re: [openstack-dev] [cinder] Cinder with remote LVM proposal

Hi Erlon, hi Philipp thank you for your answers. I will try to explain with a real case: @Erlon: I have 2 nodes that works as a SAN with targetcli and DRBD for a raid over network. This cluster can be seen as an "ISCSI node". Furthermore, I have 2 nodes with openstack-cinder-volume (with pacemaker

[openstack-dev] [cinder] Additional Grenade jobs for Cinder patches

Hi, We now have two additional gate jobs which can be used to test patches that modify RPC API, objects or DB Schema for incompatibilities. These two jobs are non-voting and can be invoked on cinder patches by typing “check experimental” as a comment on that patch. The two-additional gate jobs

[openstack-dev] [Cinder][Manila]share or volume's size unit

Hi guys, We know the share's size unit is in gigabiyte in manila, and volume's size unit is also in gigabiyte in cinder, But there is a question that the size is not exactly after we migrate tradition enviroment to OpenStack. For example: 1.There is original volume(vol_1) with 500MB size in tradit

[openstack-dev] [cinder][nova] Update attachments on replication failover

Hey Everyone, Something I've been looking at with Cinder's replication (sort of the next step in the evolution if you will) is the ability to refresh/renew in-use volumes that were part of a migration event. We do something similar with extend-volume on the Nova side through the use of Instance A

Re: [openstack-dev] [cinder][ptg] PTG Summary Now Available ...

Jay, thanks a lot for this great summary! Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Mar 6, 2018 at 10:02 PM, Jay S Bryant wrote: > Team, > > I have collected all of our actions and agreements out of the three days > of etherpads into the following summary page: [1] . The etherp

[openstack-dev] [cinder][summit] Forum topic proposal etherpad created ...

All, I just wanted to share the fact that I have created the etherpad for proposing topics for the Vancouver Forum.  [1] Please take a few moments to add topics there.  I will need to propose the topics we have in the next two weeks so this will need attention before that point in time. Th

Re: [openstack-dev] [cinder][ptg] PTG Summary Now Available ...

Thanks Jay, that helps a lot! 2018-03-06 18:46 GMT-03:00 Ivan Kolodyazhny : > Jay, thanks a lot for this great summary! > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Tue, Mar 6, 2018 at 10:02 PM, Jay S Bryant > wrote: > >> Team, >> >> I have collected all of our actions and ag

[openstack-dev] [cinder] Support share backup to different projects?

Now Cinder can transfer volume (with or without snapshots) to different projects, and this make it possbile to transfer data across tenant via volume or image. Recently we had a conversation with our customer from Germany, they mentioned they are more pleased if we can support transfer data accros

[openstack-dev] [cinder][nova] about re-image the volume

Hi,all This is the spec [0] about rebuild the volumed backed server.The question raised in the spec is about how to bandle the root volume.Finally,in Nova team,we think that the cleanest / best solution to this is to add a volume action API to cinder for re-imaging the volume.Once that i

[openstack-dev] [cinder] [placement] cinder + placement forum session etherpad

I've started an etherpad for the forum session in Vancouver devoted to discussing the possibility of tracking and allocation resources in Cinder using the Placement service. This is not a done deal. Instead the session is to discuss if it could work and how to make it happen if it seems like a go

[openstack-dev] [cinder] Project Team Dinner at Vancouver Summit

Team, We discussed having a team dinner like we have done in the past during today's team meeting.  It sounded like most people would be available Tuesday evening, so that is the evening I am planning for. If you are able to attend please add your name to the etherpad [1] by Sunday 5/20 so t

[openstack-dev] [Cinder] Pending removal of Tintri volume driver

The Cinder policy for driver CI requires that all volume drivers have a CI reporting on any new patchset. CI's may have some down time, but if they do not report within a two week period they are considered out of compliance with our policy. This is a notification that the Tintri OpenStack CI is o

[openstack-dev] [Cinder] Pending removal of Tegile volume driver

The Cinder policy for driver CI requires that all volume drivers have a CI reporting on any new patchset. CI's may have some down time, but if they do not report within a two week period they are considered out of compliance with our policy. This is a notification that the Tegile OpenStack CI is o

[openstack-dev] [Cinder] Pending removal of Scality volume driver

The Cinder policy for driver CI requires that all volume drivers have a CI reporting on any new patchset. CI's may have some down time, but if they do not report within a two week period they are considered out of compliance with our policy. This is a notification that the Scality OpenStack CI is

[openstack-dev] [cinder] [nova] locking concern with os-brick

A devstack patch was pushed earlier this cycle around os-brick - https://review.openstack.org/341744 Apparently there are some os-brick operations that are only safe if the nova and cinder lock paths are set to be the same thing. Though that hasn't yet hit release notes or other documentation yet

[openstack-dev] [cinder][drivers] Backend and volume health reporting

Hi all, I would like to propose working on a new feature for Ocata to provide health information for Cinder backends and volumes. Currently, a volume's status basically reflects the last management operation performed on it - it will be in error state only as a result of a failed management operat

Re: [openstack-dev] [cinder]concerns on driver deprecation policy

On Thu, Aug 18, 2016 at 03:44:10AM +, Husheng (TommyLike, R&D IT&Tools Equipment Dept) wrote: > Hi all, > Sorry for absence from IRC meeting of this week and put forward this topic on > driver deprecation policy again. Actually I support the driver support tag > policy completely, it's a rea

Re: [openstack-dev] [cinder] [nova] API interaction changes overview

On 9/1/2016 4:09 PM, Ildiko Vancsa wrote: Hi All, As we skipped a few meetings and we also reached the N-3 milestone this week I would like to summarise where we are currently with our plans. At the beginning of the Newton cycle we decided to refactor the Cinder API around attach and detach

Re: [openstack-dev] [cinder] [nova] API interaction changes overview

There's also another API limitation to be fixed - whether it goes in the initial API fixup or gets done later, which is a round one cinder serving multiple nova or other consumers: https://review.openstack.org/#/c/362637/ On 2 September 2016 at 22:51, Matt Riedemann wrote: > On 9/1/2016 4:09 PM,

Re: [openstack-dev] [cinder] [nova] API interaction changes overview

> On 03 Sep 2016, at 20:07, Duncan Thomas wrote: > > There's also another API limitation to be fixed - whether it goes in the > initial API fixup or gets done later, which is a round one cinder serving > multiple nova or other consumers: https://review.openstack.org/#/c/362637/ >

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

On 09/06/2016 05:27 PM, Alon Marx wrote: > I want to share our plans to open the IBM Storage driver source code. > Historically we started our way in cinder way back (in Essex if I'm > not mistaken) with just a small piece of code in the community while > keeping most of the driver code closed. S

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

On Tue, Sep 6, 2016 at 9:27 AM, Alon Marx wrote: > I want to share our plans to open the IBM Storage driver source code. > Historically we started our way in cinder way back (in Essex if I'm not > mistaken) ​You're mistaken, Cinder didn't exist at that time... but it's irrelevant. ​ > with jus

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

On 9/7/2016 8:47 AM, John Griffith wrote: On Tue, Sep 6, 2016 at 9:27 AM, Alon Marx mailto:alo...@il.ibm.com>> wrote: I want to share our plans to open the IBM Storage driver source code. Historically we started our way in cinder way back (in Essex if I'm not mistaken) ​You're mis

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

There are a number of drivers that require closed-source tools to communicate with the storage. 3 others that I've come across recently: - EMC VNX: requires Navisphere CLI v7.32 or higher - Hitachi storage volume driver: requires RAID Manager Ver 01-32-03/01 or later for VSP G1000/VSP/HU

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

Avishay Traeger wrote: > There are a number of drivers that require closed-source tools to > communicate with the storage. 3 others that I've come across recently: > > * EMC VNX: requires Navisphere CLI v7.32 or higher > * Hitachi storage volume driver: requires RAID Manager Ver 01-32-03/01 >

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

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 I've come across recently: > > > > * EMC VNX: requires Navisphere CLI v7.32 or higher >

<    5   6   7   8   9   10   11   12   13   14   >