Re: [openstack-dev] [cinder] Berlin Forum Proposals

i Jay, Yup, it makes sense. I moved the contents and updated the wiki to point to your etherpad. > Thanks for catching this mistake! > It was my mistake for not mentioning the existing etherpad during the PTG... XD Cheers, Gorka. > Jay > > > On 9/19/2018 4:42 AM, Gorka Egu

Re: [openstack-dev] [ptg][cinder] Stein PTG Summary Page Ready ...

On 18/09, Jay S Bryant wrote: > Team, > > I have put together the following page with a summary of all our discussions > at the PTG: https://wiki.openstack.org/wiki/CinderSteinPTGSummary > > Please review the contents and let me know if anything needs to be changed. > > Jay > > Hi Jay, Thank you

Re: [openstack-dev] [cinder] Berlin Forum Proposals

On 18/09, Jay S Bryant wrote: > Team, > > I have created an etherpad for our Forum Topic Planning: > https://etherpad.openstack.org/p/cinder-berlin-forum-proposals > > Please add your ideas to the etherpad.  Thank you! > > Jay > Hi Jay, After our last IRC meeting, a couple of weeks ago, I

Re: [openstack-dev] [ptg][cinder][placement] etherpad for this afternoon's meeting

On 11/09, Jay Pipes wrote: > Hi Jay, where is this discussion taking place? > Hi, It was on another email: Big Thompson Room on Tuesday from 15:15 to 17:00 Cheers, Gorka. > On Tue, Sep 11, 2018, 11:10 AM Jay S Bryant wrote: > > > All, > > > > I have created an etherpad to take notes during

Re: [openstack-dev] [cinder][ptg] Topics scheduled for next week ...

On 07/09, Jay S Bryant wrote: > Team, > > I have created an etherpad for each of the days of the PTG and split out the > proposed topics from the planning etherpad into the individual days for > discussion: [1] [2] [3] > > If you want to add an additional topic please add it to Friday or find some

Re: [openstack-dev] [Openstack-operators] [nova][cinder][neutron] Cross-cell cold migration

On 29/08, Matt Riedemann wrote: > On 8/29/2018 3:21 PM, Tim Bell wrote: > > Sounds like a good topic for PTG/Forum? > > Yeah it's already on the PTG agenda [1][2]. I started the thread because I > wanted to get the ball rolling as early as possible, and with people that > won't attend the PTG

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

On 24/08, Jay S Bryant wrote: > > > On 8/23/2018 12:07 PM, Gorka Eguileor wrote: > > On 23/08, Dan Smith wrote: > > > > I think Nova should never have to rely on Cinder's hosts/backends > > > > information to do migrations or any other operation. > &

Re: [openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

On 24/08, Matt Riedemann wrote: > On 8/22/2018 4:46 AM, Gorka Eguileor wrote: > > The solution is conceptually simple. We add a new API microversion in > > Cinder that adds and optional parameter called "generic_keep_source" > > (defaults to False) to bot

Re: [openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

On 25/08, Sean McGinnis wrote: > On Fri, Aug 24, 2018 at 04:20:21PM -0500, Matt Riedemann wrote: > > On 8/20/2018 10:29 AM, Matthew Booth wrote: > > > Secondly, is there any reason why we shouldn't just document then you > > > have to delete snapshots before doing a volume migration? Hopefully > >

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

On 23/08, Dan Smith wrote: > > I think Nova should never have to rely on Cinder's hosts/backends > > information to do migrations or any other operation. > > > > In this case even if Nova had that info, it wouldn't be the solution. > > Cinder would reject migrations if there's an incompatibility

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

On 22/08, Matt Riedemann wrote: > Hi everyone, > > I have started an etherpad for cells topics at the Stein PTG [1]. The main > issue in there right now is dealing with cross-cell cold migration in nova. > > At a high level, I am going off these requirements: > > * Cells can shard across flavors

Re: [openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

On 22/08, Matthew Booth wrote: > On Wed, 22 Aug 2018 at 10:47, Gorka Eguileor wrote: > > > > On 20/08, Matthew Booth wrote: > > > For those who aren't familiar with it, nova's volume-update (also > > > called swap volume by nova devs) is the nova part of the >

Re: [openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

On 22/08, Sean McGinnis wrote: > > > > The solution is conceptually simple. We add a new API microversion in > > Cinder that adds and optional parameter called "generic_keep_source" > > (defaults to False) to both migrate and retype operations. > > > > This means that if the driver optimized

Re: [openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

On 20/08, Matthew Booth wrote: > For those who aren't familiar with it, nova's volume-update (also > called swap volume by nova devs) is the nova part of the > implementation of cinder's live migration (also called retype). > Volume-update is essentially an internal cinder<->nova api, but as >

Re: [openstack-dev] [cinder][nova] Proper behavior for os-force_detach

On 17/07, Sean McGinnis wrote: > On Tue, Jul 17, 2018 at 04:06:29PM -0300, Erlon Cruz wrote: > > Hi Cinder and Nova folks, > > > > Working on some tests for our drivers, I stumbled upon this tempest test > > 'force_detach_volume' > > that is calling Cinder API passing a 'None' connector. At the

Re: [openstack-dev] [cinder] about block device driver

.org/p/cinder-rocky-meeting-agendas > > ------ Original -- > From: "Gorka Eguileor"; > Date: 2018年7月16日(星期一) 下午5:20 > To: "OpenStack Developmen"; > Subject: Re: [openstack-dev] [cinder] about block device driver > > > On 1

Re: [openstack-dev] [openstack-community] Give cinder-backup more CPU resources

On 06/07, Amy Marrich wrote: > Hey, > > Forwarding to the Dev list as you may get a better response from there. > > Thanks, > > Amy (spotz) > Hi, I included a good number of improvements regarding bottlenecks on the backup service in recent releases, some of them are automatic, and others need

Re: [openstack-dev] [cinder] about block device driver

On 16/07, Rambo wrote: > Hi,all > > > In the Cinder repository, I noticed that the BlockDeviceDriver driver is > being deprecated, and was eventually be removed with the Queens release. > > > https://github.com/openstack/cinder/blob/stable/ocata/cinder/volume/drivers/block_device.py > > > In

[openstack-dev] [Cinder] Reusing Cinder drivers' code directly without running Cinder: In our applications, from Ansible, and for Containers

Hi, During the last OpenStack PTG, I announced in the Cinder room the development of cinderlib, and explained how this library allowed any Python application to use Cinder storage drivers (there are over 80) without running any services. This takes the standalone effort one step further. Now you

Re: [openstack-dev] [oslo.db] innodb OPTIMIZE TABLE ?

On 09/04, Michael Bayer wrote: > On Mon, Apr 9, 2018 at 5:53 AM, Gorka Eguileor <gegui...@redhat.com> wrote: > > On 06/04, Michael Bayer wrote: > >> On Wed, Apr 4, 2018 at 5:00 AM, Gorka Eguileor <gegui...@redhat.com> wrote: > >> > On 03/04, Jay Pipes wrot

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

On 09/04, Sean McGinnis wrote: > On Mon, Apr 09, 2018 at 07:00:56PM +0100, Duncan Thomas wrote: > > Hopefully this flow means we can do rebuild root filesystem from > > snapshot/backup too? It seems rather artificially limiting to only do > > restore-from-image. I'd expect restore-from-snap to be

Re: [openstack-dev] [oslo.db] innodb OPTIMIZE TABLE ?

On 06/04, Michael Bayer wrote: > On Wed, Apr 4, 2018 at 5:00 AM, Gorka Eguileor <gegui...@redhat.com> wrote: > > On 03/04, Jay Pipes wrote: > >> On 04/03/2018 11:07 AM, Michael Bayer wrote: > >> > The MySQL / MariaDB variants we use nowadays default to > &g

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

On 06/04, Matt Riedemann wrote: > On 4/6/2018 5:09 AM, Matthew Booth wrote: > > I think you're talking at cross purposes here: this won't require a > > swap volume. Apart from anything else, swap volume only works on an > > attached volume, and as previously discussed Nova will detach and > >

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

On 05/04, Matt Riedemann wrote: > On 4/5/2018 3:15 AM, Gorka Eguileor wrote: > > But just to be clear, Nova will have to initialize the connection with > > the re-imagined volume and attach it again to the node, as in all cases > > (except when defaulting to downloading

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

On 04/04, Matt Riedemann wrote: > On 4/2/2018 6:59 AM, Gorka Eguileor wrote: > > I can only see one benefit from implementing this feature in Cinder > > versus doing it in Nova, and that is that we can preserve the volume's > > UUID, but I don't think this is even relevant

Re: [openstack-dev] [oslo.db] innodb OPTIMIZE TABLE ?

On 03/04, Jay Pipes wrote: > On 04/03/2018 11:07 AM, Michael Bayer wrote: > > The MySQL / MariaDB variants we use nowadays default to > > innodb_file_per_table=ON and we also set this flag to ON in installer > > tools like TripleO. The reason we like file per table is so that > > we don't grow

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

On 29/03, Sean McGinnis wrote: > > 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

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

ions I can think of go through Glance images, which is the right way to share volume data between users. I think our efforts would be better spent removing the bottlenecks we currently have on all create volume from source operations if what the customer is trying to do is workaround it via the backups. Chee

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

On 20/03, Jay S Bryant wrote: > > > On 3/19/2018 10:55 PM, TommyLike Hu wrote: > > 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

Re: [openstack-dev] [cinder] [manila] Performance concern on new quota system

On 09/03, Sean McGinnis wrote: > > > On Mar 9, 2018, at 07:37, TommyLike Hu wrote: > > > > Thanks Gorka, > > To be clear, I started this discussion not because I reject this > > feature, instead I like it as it's much more clean and simple, compared > > with

Re: [openstack-dev] [cinder] [manila] Performance concern on new quota system

On 09/03, TommyLike Hu wrote: > Hey all, > During the Cinder and Manila's cross project discussion on quota system > last week, I raise our concern of performance impact on the count resource > feature, and Gorka pointed out we might miss some of the indexes when > testing. So I reshaped the

Re: [openstack-dev] [cinder] Cinder volume revert to snapshot with Ceph

On 06/03, 李杰 wrote: > Hi,all > > > This is the patch [0] about volume revert to snapshot with Ceph.Is > anyone working on this patchset or maybe new patchset was proposed to > implement RBD specific functionality?Can you tell me more about this ?Thank > you very much. > The link is

Re: [openstack-dev] [glance][cinder]Question about cinder as glance store

to be properly setup. Cheers, Gorka. > 2018-02-07 8:27 GMT-02:00 Gorka Eguileor <gegui...@redhat.com>: > > > On 07/02, Rikimaru Honjo wrote: > > > Hello, > > > > > > I'm planning to use cinder as glance store. > > > And, I'll setup cinder to co

Re: [openstack-dev] [glance][cinder]Question about cinder as glance store

On 07/02, Rikimaru Honjo wrote: > Hello, > > I'm planning to use cinder as glance store. > And, I'll setup cinder to connect storage by iSCSI multipath. > > In this case, can I run glance-api and cinder-volume on the same node? > > In my understanding, glance-api will attach a volume to own node

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

On 12/12, gordon chung wrote: > hi, > > i'm attempting to add support for the cinder capacity notifications that > were added a while back[1]. > > adding measurement support in ceilometer is pretty simple where in most > cases you just add an entry to a yaml file[2]. the problem i have right > now

Re: [openstack-dev] May I run iscsiadm --op show & update 100 times?

On 03/10, Rikimaru Honjo wrote: > Hello Gorka, > > On 2017/10/02 20:37, Gorka Eguileor wrote: > > On 02/10, Rikimaru Honjo wrote: > > > Hello, > > > > > > I'd like to discuss about the following bug of os-brick. > > > > > > * os-br

Re: [openstack-dev] [cinder][nova]May I run iscsiadm --op show & update 100 times?

artup values to "automatic" if we use iscsi. > 3. "iscsiadm -m discovery" command will recreate iscsi node repositories.[1] >As a result, node.startup values of already attached volumes will be revert >to default(=manual). > > Gorka Eguileor and I discussed how d

Re: [openstack-dev] Identify Openstack commands and manipulate them

On 03/07, david jhon wrote: > Thanks for the help. > > Openstack commands mean some administrative commands as listed here: > > https://docs.openstack.org/developer/python-openstackclient/command-objects/server.html > > I want to identify incoming openstack server commands on controller machine >

Re: [openstack-dev] [OpenStack][Cinder][backup]Get total files/objects disk size of backup

On 30/06, int32bit wrote: > Currently the size in backup is src volume size rather than backup > file/object size, it's used to record original volume size that avoid > damaging target in restore operation if the volume has been resized. > > But it may be more useful for end user to tell them

Re: [openstack-dev] [cinder][nova][os-brick] Testing for proposed iSCSI OS-Brick code

On 31/05, Matt Riedemann wrote: > On 5/31/2017 6:58 AM, Gorka Eguileor wrote: > > Hi, > > > > As some of you may know I've been working on improving iSCSI connections > > on OpenStack to make them more robust and prevent them from leaving > > left

[openstack-dev] [cinder][nova][os-brick] Testing for proposed iSCSI OS-Brick code

Hi, As some of you may know I've been working on improving iSCSI connections on OpenStack to make them more robust and prevent them from leaving leftovers on attach/detach operations. There are a couple of posts [1][2] going in more detail, but a good summary would be that to fix this issue we

Re: [openstack-dev] [cinder] Is Cinder still maintained?

On 27/04, Julien Danjou wrote: > Hi, > > I've posted a refactoring patch that simplifies tooz (read: remove > technical debt) usage more than a month ago, and I got 0 review since > then: > > https://review.openstack.org/#/c/447079 > > I'm a bit worried to see this zero review on such patches.

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

On 21/04, Jae Sang Lee wrote: > 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,

Re: [openstack-dev] [neutron][gate] functional job busted

On 14/03, Ihar Hrachyshka wrote: > Hi all, > > the patch that started to produce log index file for logstash [1] and > the patch that switched metadata proxy to haproxy [2] landed and > together busted the functional job because the latter produces log > messages with null-bytes inside, while

Re: [openstack-dev] [Cinder] BlockDeviceDriver deprecated?

On 03/02, Pieter Baele wrote: > Red Hat tells me the Cinder BlockDeviceDriver is going to be deprecated > upstream. It isn't supported in RHOSP in any case. > Is this true? Yes, that is correct, it's in the release notes:

Re: [openstack-dev] [cinder]Using DEFAULT section to configure drivers is not supported since Ocata

On 02/02, Gyorgy Szombathelyi wrote: > Hi! > > Because of the deprecated driver configuration in the DEFAULT section doesn't > work anymore in Ocata, I would like to ask if any migration tool exists for > using the previously created volumes? > > E.g. if the existing volumes have the attribute

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

On 07/10, 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 need to be pulled from > the cinder

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

> > On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant > > > <jsbry...@electronicjungle.net <mailto:jsbry...@electronicjungle.net>> > > > wrote: > > > > > > +1 from me. It is making good progress and is low risk. > > > > &

Re: [openstack-dev] Spain Visa for Indian contributors

Hi, As a native Spanish speaker I offer my help with the translation if needed. I assume the OpenStack visa team would be the one required to issue the translated invitation letter for it to be valid. Cheers, Gorka. On Thu, Sep 15, 2016 at 2:14 PM, M Ranga Swami Reddy

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

AM, Jay S. Bryant > > > <jsbry...@electronicjungle.net <mailto:jsbry...@electronicjungle.net>> > > > wrote: > > > > > > +1 from me. It is making good progress and is low risk. > > > > > > -Jay > > > > > > >

[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] Nominating Scott D'Angelo to Cinder core

+2 Congrats Scott!! On 27/06, Sean McGinnis wrote: > 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

Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 23/05, Ivan Kolodyazhny wrote: > Hi developers and operators, > I would like to get any feedback from you about my idea before I'll start > work on spec. > > In Nova, we've got max_concurrent_builds option [1] to set 'Maximum number > of instance builds to run concurrently' per each compute.

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

On 03/05, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions [1] have > been significant for some time now. > > His persistence with versioned objects has been

Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit

On 16/03, D'Angelo, Scott wrote: > I can do a presentation on microversions. > "I love it when a plan comes together". This one had your name written all over it. ;-) > > > Scott D'Angelo (scottda) > > -- Original Message -- > From : Gorka E

Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit

On 15/03, Michał Dulko wrote: > On 03/14/2016 09:52 PM, Gorka Eguileor wrote: > > Hi, > > > > As you all probably know, during this cycle we have introduced quite a > > big number of changes in cinder that will have a great impact in the > > development of the new

Re: [openstack-dev] [all] Maintaining httplib2 python library

On 14/03, Sean McGinnis wrote: > On Mon, Mar 14, 2016 at 10:37:52AM -0400, Sean Dague wrote: > > On 03/14/2016 10:24 AM, Ian Cordasco wrote: > > > > > > > > > -Original Message- > > > From: Davanum Srinivas > > > Reply: OpenStack Development Mailing List (not for

[openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit

Hi, As you all probably know, during this cycle we have introduced quite a big number of changes in cinder that will have a great impact in the development of the new functionality as well as changes to existing ones moving forward from an implementation perspective. These changes to the cinder

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

Thanks for your leadership Sean, I think you've done a terrific job. Gorka. On 11/03, Sean McGinnis wrote: > Hey everyone, > > Wow, how six months flies! I'd like to announce my candidacy to continue on as > Cinder PTL for the Newton release cycle. > > A lot has been accomplished in the

Re: [openstack-dev] [cinder] Nested quota -1 limit race condition

On 03/03, Ryan McNair wrote: > Hey all, > > Nested quotas has officially started fighting back - while writing Tempest > tests for the nested quota support [1], I hit a race-condition related to > the nested quota -1 support that has me stumped. I opened a bug for it [2] > with more details, but

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 02/03, Ivan Kolodyazhny wrote: > I'll try to implement such scenario and step-by-step guideline soon. > That would be fantastic!! Thank you very much Looking forward to it. :-) Cheers, Gorka. > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Wed, Mar 2, 2016 at 5:16 PM, Eric

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 02/03, Ivan Kolodyazhny wrote: > Eric, > > There are Gorka's patches [10] to remove API Races > > > [10] > https://review.openstack.org/#/q/project:openstack/cinder+branch:master+topic:fix/api-races-simplified > I looked at Rally a long time ago so apologies if I'm totally off base here,

Re: [openstack-dev] [Cinder][DRBD] questions about pep8/flake8 etc.

On 21/12, Walter A. Boring IV wrote: > On 12/21/2015 06:40 AM, Philipp Marek wrote: > >Hi everybody, > > > >in the current patch https://review.openstack.org/#/c/259973/1 the test > >script needs to use a lot of the constant definitions of the backend driver > >it's using (DRBDmanage). > > > >As

Re: [openstack-dev] [cinder] Custom fields for versioned objects

On 15/12, Ryan Rossiter wrote: > Thanks for the review Michal! As for the bp/bug report, there’s four options: > > 1. Tack the work on as part of bp cinder-objects > 2. Make a new blueprint (bp cinder—object-fields) I think #2 would be the best option, as this is not part of the effort to move

Re: [openstack-dev] [Cinder] Is there anyone truly working on this issue https://bugs.launchpad.net/cinder/+bug/1520102?

On 11/12, mtanino wrote: > Hi Thang, Vincent, > > I guess the root cause is that finish_volume_migration() still > handles a volume as a dictionary instead of volume object and > the method returns dict volume. > > And then, 'rpcapi.delete_volume()' in migrate_volume_completion() > tries to

Re: [openstack-dev] Is there any way I can completely erase all the data when deleting a cinder volume

On 18/11, Young Yang wrote: > There are some sensitive data in my volume. > I hope openstack can completely erase all the data (e.g. overwrite the > whole volume will 0 bits) when deleting a cinder volume. > > I plan to write some code to make Openstack to mount that volume and > rewrite the

[openstack-dev] [cinder] Specifications to support High Availability Active-Active configurations in Cinder

Hi, We finally have ready for review all specifications required to support High Availability Active/Active configurations in Cinder's Volume nodes. There is a Blueprint to track this effort [1] and the specs are as follow: - General description of the issues and solutions [2] - Removal of

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

On 28/09, John Griffith wrote: > On Mon, Sep 28, 2015 at 6:19 PM, Mark Voelker wrote: > > > FWIW, the most popular client libraries in the last user survey[1] other > > than OpenStack’s own clients were: libcloud (48 respondents), jClouds (36 > > respondents), Fog (34

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

Anyway, it's a matter of opinion and afaik in Cinder we don't even have a real problem with downvoting for the commit message length, I don't see more than 1 every couple of months or so. Cheers, Gorka. > > > On Mon, Sep 28, 2015 at 11:00 PM, Assaf Muller <amul...@redhat.com

Re: [openstack-dev] [Cinder] [Manila] Will NFS stay with Cinder as a reference implementation?

On 29/09, Duncan Thomas wrote: > Cinder provides a block storage abstraction to a vm. Manila provides a > filesystem abstraction. The two are very different, and complementary. I > see no reason why the nfs related cinder drivers should be removed based on > the existence or maturity of manila -

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 28/09, Andreas Jaeger wrote: > On 2015-09-28 11:47, Gorka Eguileor wrote: > >On 26/09, Morgan Fainberg wrote: > >>As a core (and former PTL) I just ignored commit message -1s unless there > >>is something majorly wrong (no bug id where one is needed, etc). > >

Re: [openstack-dev] [cinder] How to make a mock effactive for all method of a testclass

On 23/09, Eric Harney wrote: > On 09/23/2015 04:06 AM, liuxinguo wrote: > > Hi, > > > > In a.py we have a function: > > def _change_file_mode(filepath): > > utils.execute('chmod', '600', filepath, run_as_root=True) > > > > In test_xxx.py, there is a testclass: > > class

Re: [openstack-dev] [cinder] How to make a mock effactive for all method of a testclass

On 23/09, liuxinguo wrote: > Hi, > > In a.py we have a function: > def _change_file_mode(filepath): > utils.execute('chmod', '600', filepath, run_as_root=True) > > In test_xxx.py, there is a testclass: > class DriverTestCase(test.TestCase): > def test_a(self) > ... > Call a.

Re: [openstack-dev] [cinder] L3 low pri review queue starvation

On Tue, Sep 01, 2015 at 09:30:26AM -0600, John Griffith wrote: > On Tue, Sep 1, 2015 at 5:57 AM, Tom Barron wrote: > > > [Yesterday while discussing the following issue on IRC, jgriffith > > suggested that I post to the dev list in preparation for a discussion in > >

Re: [openstack-dev] [cinder] Midcycle Sprint Summary

On Mon, Aug 17, 2015 at 08:53:29AM -0700, Mike Perez wrote: A *summary* of the Cinder midcycle sprint, in attempt to keep your attention. Full meeting notes available [1]. [ ... ] -- Mike Perez Thank you very much for the summary. Cheers, Gorka.

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Tue, Aug 04, 2015 at 08:30:17AM -0700, Joshua Harlow wrote: Duncan Thomas wrote: On 3 August 2015 at 20:53, Clint Byrum cl...@fewbar.com mailto:cl...@fewbar.com wrote: Excerpts from Devananda van der Veen's message of 2015-08-03 08:53:21 -0700: Also on a side note, I think

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Tue, Aug 04, 2015 at 08:40:13AM -0700, Joshua Harlow wrote: Clint Byrum wrote: Excerpts from Devananda van der Veen's message of 2015-08-03 08:53:21 -0700: On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlowharlo...@outlook.com wrote: Clint Byrum wrote: Excerpts from Gorka Eguileor's message

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Tue, Aug 04, 2015 at 10:32:40AM +0300, Duncan Thomas wrote: On 3 August 2015 at 20:53, Clint Byrum cl...@fewbar.com wrote: Excerpts from Devananda van der Veen's message of 2015-08-03 08:53:21 -0700: Also on a side note, I think Cinder's need for this is really subtle, and one could

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

of Tooz, where we want it and for how long we'll be using it in each of those places. To answer those questions all that's needed is to read this thread and the links referred on some conversations. Gorka. Thanks, Kevin From: Gorka Eguileor [gegui

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

on this thread. Cheers, Gorka. Thanks, Kevin From: Gorka Eguileor Sent: Tuesday, August 04, 2015 1:39:07 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active On Mon

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

-to-cinder-active-active/ As well as on IRC and this thread, I don't see the point of repeating it over and over again, at some point people need to start doing their homework and read what's already been said to get up to speed on the topic so we can move on. Gorka. From: Gorka Eguileor [gegui

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Mon, Aug 03, 2015 at 12:28:27AM -0700, Clint Byrum wrote: Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700: On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote: On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor gegui...@redhat.com wrote: I know we've all

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Fri, Jul 31, 2015 at 03:18:39PM -0700, Clint Byrum wrote: Excerpts from Mike Perez's message of 2015-07-31 10:40:04 -0700: On Fri, Jul 31, 2015 at 8:56 AM, Joshua Harlow harlo...@outlook.com wrote: ...random thought here, skip as needed... in all honesty orchestration solutions like

Re: [openstack-dev] [Cinder][Ironic] A possible solution for HA Active-Active

On Fri, Jul 31, 2015 at 12:47:34PM -0700, Joshua Harlow wrote: Joshua Harlow wrote: Mike Perez wrote: On Fri, Jul 31, 2015 at 8:56 AM, Joshua Harlowharlo...@outlook.com wrote: ...random thought here, skip as needed... in all honesty orchestration solutions like mesos

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Mon, Aug 03, 2015 at 10:22:42AM +0200, Thierry Carrez wrote: Flavio Percoco wrote: [...] So, to summarize, I love the effort behind this. But, as others have mentioned, I'd like us to take a step back, run this accross teams and come up with an opinonated solution that would work for

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Mon, Aug 03, 2015 at 07:01:45PM +1000, Morgan Fainberg wrote: Lets step back away from tooz. Tooz for the sake of this conversation is as much the same as saying zookeeper or consul or etcd, etc. We should be focused (as both Flavio and Thierry said) on if we need DLM and what it will

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

that fixes everything and gives us HA A-A on its own, then I believe they are a little bit lost. Gorka. Thanks, Kevin From: Gorka Eguileor [gegui...@redhat.com] Sent: Monday, August 03, 2015 1:43 AM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote: On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor gegui...@redhat.com wrote: I know we've all been looking at the HA Active-Active problem in Cinder and trying our best to figure out possible solutions to the different issues

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote: On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor gegui...@redhat.com wrote: I know we've all been looking at the HA Active-Active problem in Cinder and trying our best to figure out possible solutions to the different issues

Re: [openstack-dev] [all] cross project communication: Return request-id to caller

On Tue, Jul 28, 2015 at 09:48:25AM -0400, Doug Hellmann wrote: Excerpts from Gorka Eguileor's message of 2015-07-28 10:37:42 +0200: On Fri, Jul 24, 2015 at 10:08:45AM -0400, Doug Hellmann wrote: Excerpts from Kekane, Abhishek's message of 2015-07-24 06:33:00 +: Hi Devs,

Re: [openstack-dev] [all] cross project communication: Return request-id to caller

On Fri, Jul 24, 2015 at 10:08:45AM -0400, Doug Hellmann wrote: Excerpts from Kekane, Abhishek's message of 2015-07-24 06:33:00 +: Hi Devs, X-Openstack-Request-Id. We have analysed python-cinderclient, python-glanceclient, python-novaclient, python-keystoneclient and

[openstack-dev] [Cinder] A possible solution for HA Active-Active

Hi all, I know we've all been looking at the HA Active-Active problem in Cinder and trying our best to figure out possible solutions to the different issues, and since current plan is going to take a while (because it requires that we finish first fixing Cinder-Nova interactions), I've been

Re: [openstack-dev] [Cinder]Restrict volume creation based on type

On Mon, Jul 13, 2015 at 07:56:36AM +0300, Eduard Matei wrote: Hi, Forgot to mention, indeed we configured extra_specs: volume_backend_name. The problem is that a volume of this type can get scheduled on a node where c-vol is not configured with this backend. F.e.: I have 3 storage nodes

Re: [openstack-dev] [openstack][cinder]A discussion about quota update lower than current usage.

On Fri, Jul 10, 2015 at 10:28:06AM +0300, Duncan Thomas wrote: That is a semantic change to the api that will break anybody who has tooling expecting the current behavior. Since there are perfectly sensible uses of the current behavior, that is not a good thing. Hi Duncan, I don't think that

Re: [openstack-dev] [Cinder] python-cinderclient functional tests

On Mon, Jul 06, 2015 at 09:48:27PM +0300, Ivan Kolodyazhny wrote: Hi all, As you may know, we've got experimental job [1] to run functional tests [2] for python-cinderclient with devstack setup. Functional tests for python-cinderclient is very important because it's almost the only way to

Re: [openstack-dev] [Security][Bandit] Bandit gate usage

On Thu, Jul 02, 2015 at 07:09:41PM +, Kelsey, Timothy John wrote: Hello Stackers, A few intrepid projects have started adopting Bandit, an automatic security linter built by the security project, into their gate tests. This is very rewarding to see for those of us who have worked on the

Re: [openstack-dev] [cinder][oslo] Locks for create from volume/snapshot

On Mon, Jun 29, 2015 at 03:45:56PM +0300, Duncan Thomas wrote: On 29 June 2015 at 15:23, Dulko, Michal michal.du...@intel.com wrote: There’s also some similar situations when we actually don’t lock on resources. For example – a cgsnapshot may get deleted while creating a

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

On Tue, Jun 23, 2015 at 08:49:55AM -0700, Mike Perez wrote: There was a bug raised [1] from some large deployments that the Cinder client 1.2.0 and beyond is not working because of version discovery. Unfortunately it's not taking into account of deployments that have a proxy. A little bit

Re: [openstack-dev] [oslo] Updates from the Summit

On Wed, May 27, 2015 at 08:47:42AM -0400, Davanum Srinivas wrote: Hi Team, Here are the etherpads from the summit[1]. I remember that in Taskflow's Fishbowl session we discussed not only pause/yield option but abort/cancel for long running tasks as well, but reviewing the Etherpad now I don't

Re: [openstack-dev] [Cinder] [Nova] Quota delete API behavior and incorrect Quota usage reported after deletion

On Wed, Apr 08, 2015 at 10:13:27PM +0200, Gorka Eguileor wrote: Hi all, This message is in relation with a bug on Quota deletion API that affects both Nova [1] and Cinder [2], so we should discuss together what's the desired solution as to be consistent in both projects. Currently Quota

  1   2   >