Re: [openstack-dev] Gerrit tooling improvements(was Re: auto-abandon changesets considered harmful)

that currently get incorrectly hit by auto-abandon. -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [tempest][glusterfs] Online Snapshot fails with GlusterFS

I'm assuming your mean the following lines in nova policy.js: compute_extension:os-assisted-volume-snapshots:create:rule:admin_api, compute_extension:os-assisted-volume-snapshots:delete:rule:admin_api These 2 calls are not intended to be made directly via an end user, but via cinder, as a

Re: [openstack-dev] [cinder] Decision related to cinder metadata

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

Re: [openstack-dev] what code in cinder volume driver supports volume migration between two backends of same type but having different volume types? [cinder]

volume migration then it would be good for new folks in cinder. Regards Nikesh On Sun, Mar 1, 2015 at 10:12 PM, Duncan Thomas duncan.tho...@gmail.com wrote: Migrate - move between backends of the same volume type Retype - move between types. Will migrate the volume for you if necessary

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

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

Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI

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

Re: [openstack-dev] what code in cinder volume driver supports volume migration between two backends of same type but having different volume types? [cinder]

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

Re: [openstack-dev] H302 considered harmful

Thanks for that, Joe. I'd say the cons miss 'It looks ugly in places'. On 25 February 2015 at 20:54, Joe Gordon joe.gord...@gmail.com wrote: On Wed, Feb 25, 2015 at 10:51 AM, Duncan Thomas duncan.tho...@gmail.com wrote: Hi So a review [1] was recently submitted to cinder to fix up all

[openstack-dev] H302 considered harmful

readable, Is there anybody who'd like to step forward in defence of this rule and explain why it is an improvement? I don't discount for a moment the possibility I'm missing something, and welcome the education in that case Thanks [1] https://review.openstack.org/#/c/145780/ -- Duncan Thomas

Re: [openstack-dev] H302 considered harmful

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

Re: [openstack-dev] [nova] Outcome of the nova FFE meeting for Kilo

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

Re: [openstack-dev] [all][oslo] Dealing with database connection sharing issues

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

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

on this, and to all of the various people in both cinder and infra who've been very active in helping people get their CI running, sometimes in very trying circumstances. -- Duncan Thomas __ OpenStack Development Mailing List

Re: [openstack-dev] [nova] Request Spec Freeze Exception (DRBD for Nova)

+1 Very excited to see this in and usable Duncan Thomas On Jan 30, 2015 2:56 AM, Philipp Marek philipp.ma...@linbit.com wrote: Hi all, in Paris (and later on, on IRC and the mailing list) I began to ask around about providing a DRBD storage driver for Nova. This is an alternative

Re: [openstack-dev] The Evolution of core developer to maintainer?

the expectation that your feature (or even contentious bug fix) is likely to get merged in days - the project is sufficiently big that that is in fact unlikely. -- Duncan Thomas __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [cinder] volume driver for Blockbridge EPS backend

On 11 Apr 2015 02:04, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-04-11 01:28:51 +0300 (+0300), Duncan Thomas wrote: [...] We will not be merging any drivers without stable 3rd party CI in future [...] For clarity, hopefully this is stable testing reporting on changes to the project

Re: [openstack-dev] [cinder] volume driver for Blockbridge EPS backend

On 11 Apr 2015 02:04, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-04-11 01:28:51 +0300 (+0300), Duncan Thomas wrote: [...] We will not be merging any drivers without stable 3rd party CI in future [...] For clarity, hopefully this is stable testing reporting on changes to the project

Re: [openstack-dev] [Cinder] Query on adding new table to cinder DB

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

Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver

Can you please investigate and comment here on this thread as to why your CI is failing for all patches? If this is not resolved, your driver will not be re-added, and ignoring requests to investigate CI failures will increase the chances of your driver being removed in future, without notice.

Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver

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

Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver

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

Re: [openstack-dev] [Neutron] [Nova] [Cinder] [tc] Should Openstack project maintained by core team keep only API/DB in the future?

On 28 April 2015 at 21:59, Kevin Benton blak...@gmail.com wrote: The concern is that having broken drivers out there that claim to work with an OpenStack project end up making the project look bad. It's similar to a first time Linux user experiencing frequent kernel panics because they are

Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver

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

Re: [openstack-dev] [Neutron] [Nova] [Cinder] [tc] Should Openstack project maintained by core team keep only API/DB in the future?

Neutron closely enough that I can comment on how this might/might not affect them. -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [cinder][nova] Question on Cinder client exception handling

it? Seems like the right approach to me. In some cases, the cinder API will need to return more info first. I suggest raising bugs for any situations that are hard to detect, and we can work from there... -- Duncan Thomas

Re: [openstack-dev] [nova] [cinder] API service in service group API

In the case of cinder, there is a proposal to add it in, since it makes some of the versioning work easier On 8 May 2015 15:08, Dulko, Michal michal.du...@intel.com wrote: Hi, I wonder why nova-api or cinder-api aren't present service group API of each project: mdulko:devstack/ (master) $

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

more RFC compliant - nothing in the RFC prohibits this that I can spot, it's just a loose convention. -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [openstack] [cinder] Problems with existing Cinder Database Quota Driver

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

Re: [openstack-dev] [cinder] CHAP secret is visible in cinder volume log

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

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

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

Re: [openstack-dev] [cinder] Issue for backup speed

to swift compare to backup of 50 GB to swift? *From:* Duncan Thomas [mailto:duncan.tho...@gmail.com] *Sent:* Wednesday, April 01, 2015 6:13 AM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [cinder] Issue for backup speed This is something

Re: [openstack-dev] [cinder] Report status of Huawei Volume CI from April 1

As discussed on IRC, this was a config problem, and any of the newer links (with 8080 in them) should work. Thanks to Liu for following through on this. __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [cinder] Please check the log access

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

Re: [openstack-dev] [all] how to send messages (and events) to our users

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

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 8 April 2015 at 20:34, Chris Dent chd...@redhat.com wrote: On Wed, 8 Apr 2015, Sandy Walsh wrote: Yes. It would be so good to pull apart the state-machine that is Nova and just emit completed actions via notifications. Then, have something like TaskFlow externalize the orchestration. Do

Re: [openstack-dev] The Evolution of core developer to maintainer?

misunderstood the proposal further up the thread when I replied before. This sounds eminently sensible. There's certainly no hard at all in recognising large contributions other than reviews, and bug triage is almost becoming as large a job at various points in the cycle. -- Duncan Thomas

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

the workflow is, user does something. It breaks with error notify admin then admin needs to figure out why... ideally there needs to be a field for why in the db, and the dashboard can show it to admins? Thanks, Kevin -- *From:* Duncan Thomas *Sent:* Friday

Re: [openstack-dev] [cinder] volume driver for Blockbridge EPS backend

On 10 Apr 2015 21:02, Joshua Huber jhu...@blockbridge.com wrote: A couple questions: 1) When is it appropriate to submit the driver for review? Is 3rd-party CI a prerequisite? We will not be merging any drivers without stable 3rd party CI in future, so it is a requirement. You can submit the

Re: [openstack-dev] [cinder][nova] Is volume connection_info modeled/documented anywhere?

I don't think you need an entry per driver, you need an entry per connection type - iSCSI, FC, DRDB, CEPH being the ones I can think of off the top of my head On 10 Jun 2015 16:57, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: While investigating/discussing bug 1463525 [1] I remembered how

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

The problem there is that it takes (significant) time for the connection attempt to time out - every cinder command taking several minutes is not acceptable. Obviously this depends on the network setup of the cloud - I can only talk about the case we saw On 24 Jun 2015 00:25, Jeremy Stanley

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

this node is firewalled (drop packets .v. send reset), an attempt to connect to this URL can take a long time to timeout. I *think* we can get the desired behaviour by looking at the entry in the catalogue, and if it has a trailing version number then don't do discovery, but I might be wrong... -- Duncan

Re: [openstack-dev] [Cinder] Implementation of ABC MetaClasses

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

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

We are working on some sort of distributed replacement for the locks in cinder, since file locks are limiting our ability to do HA. I'm afraid you're unlikely to get any traction until that work is done. I also have a concern that some backend do not handle load well, and so benefit from the

Re: [openstack-dev] [nova] Plan to consolidate FS-style libvirt volume drivers under a common base class

On 17 June 2015 at 00:21, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all very similar. I want to extract a common base class that abstracts some of the common code and then let the sub-classes provide overrides where

Re: [openstack-dev] [nova] Plan to consolidate FS-style libvirt volume drivers under a common base class

On 17 June 2015 at 15:36, Dmitry Guryanov dgurya...@parallels.com wrote: On 06/17/2015 02:14 PM, Duncan Thomas wrote: On 17 June 2015 at 00:21, Matt Riedemann mrie...@linux.vnet.ibm.com mailto:mrie...@linux.vnet.ibm.com wrote: The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume

Re: [openstack-dev] [Manila] [Cinder] About how to hide the dummy destination record during migration

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

Re: [openstack-dev] [Manila] Expected Manila behavior for creation of share from snapshot

a transfer to a diff tenant ? Cinder doesn't seem to have any concept analogous to a share network from what I can see; the cinder transfer commands are for moving a volume between tenants, which is a different thing, I think. -- Duncan Thomas

Re: [openstack-dev] [Cinder] Quobyte Cinder Driver revert?

It was discussed on the mailing list, and at the weekly meeting. Mike had had no response on the issue from the listed contact email, and the CI was reporting failure for every patch for two months On 3 Jul 2015 17:33, Silvan Kaiser sil...@quobyte.com wrote: Hello! I just found the following

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

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 consistencygroup from it. From my perspective it seems best to have atomic

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

at 5:07 AM, Joshua Harlow harlo...@outlook.com wrote: John Griffith wrote: On Sat, Jun 27, 2015 at 11:47 AM, Joshua Harlow harlo...@outlook.com mailto:harlo...@outlook.com wrote: Duncan Thomas wrote: We are working on some sort of distributed replacement

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

, Michal wrote: That’s right, it might be painful. V3 API implememtation would be also a hard, because then we would need different manager behavior for requests from V2 and V3… So maybe we need some config flag with deprecation procedure scheduled? *From:*Duncan Thomas [mailto:duncan.tho

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

On 29 June 2015 at 18:18, Joshua Harlow harlo...@outlook.com wrote: Duncan Thomas wrote: Do we know what is so hated about the glance task API? Tasks and entity queues give the required exclusion, if you accept that tasks can fail if previous tasks in the queue can cause things to be pulled

Re: [openstack-dev] Getting rid of suds, which is unmaintained, and which we want out of Debian

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

Re: [openstack-dev] [tempest][qa][cinder] How to configure tempest with to test volume migration?

There doesn't seem to be an existing tempest test for this. I suggest writing the test so that it looks if there are two volume types defined, and if so uses them. Ideally you should test migration to and from lvm. There is offline migration (volume is available) and online migration (volume is

Re: [openstack-dev] [cinder] Port Cinder to Python 3

+topic:py3,n,z Duncan Thomas rejected one of my patch: As commented on https://review.openstack.org/#/c/185411/ I'd really like to be convinced that there's an end in sight for this python3 work, or I'm going to start rejecting it. This change is making the code noticeably harder to read, and has

Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?

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

Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?

://bugs.launchpad.net/cinder/+bug/1454244 2. “VolumeNotFound” exception error message should be consistent across all APIs Please suggest. Thanks *From:* Duncan Thomas [mailto:duncan.tho...@gmail.com] *Sent:* 26 May 2015 17:14 *To:* OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

+1 without hesitation On 22 May 2015 16:36, Mike Perez thin...@gmail.com wrote: This is long overdue, but it gives me great pleasure to nominate Sean McGinnis for Cinder core. Reviews: https://review.openstack.org/#/q/reviewer:+%22Sean+McGinnis%22,n,z Contributions:

Re: [openstack-dev] [cinder]Cinder creates encrypted volume from image

That's a bug! I'm not aware of anybody working on it, and I don't see any old bugs open for it. A suitable fix would be very welcome On 12 Aug 2015 14:54, Li, Xiaoyan xiaoyan...@intel.com wrote: Hi all, Currently when cinder creates a volume with an encrypted volume type from an image(which

Re: [openstack-dev] [cinder] Proposing Gorka Eguileor for core

+1 On 17 Aug 2015 18:51, Ivan Kolodyazhny e...@e0ne.info wrote: +1. Gorka, Thanks for your contribution! Regards, Ivan Kolodyazhny, Web Developer, http://blog.e0ne.info/, http://notacash.com/, http://kharkivpy.org.ua/ On Sat, Aug 15, 2015 at 6:25 AM, John Griffith

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

breaking normal usage. On 30 Jun 2015 19:28, John Griffith john.griffi...@gmail.com wrote: On Mon, Jun 29, 2015 at 11:58 PM, Duncan Thomas duncan.tho...@gmail.com wrote: We already have an environment variable for version... 'auto'? On 30 Jun 2015 07:57, John Griffith john.griffi...@gmail.com wrote

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

We already have an environment variable for version... 'auto'? On 30 Jun 2015 07:57, John Griffith john.griffi...@gmail.com wrote: On Mon, Jun 29, 2015 at 8:54 PM, Jay Bryant jsbry...@electronicjungle.net wrote: I too would prefer option 2. Would rather do the pack ports than remove the

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

we're very careful. I'd rather use a persistent lock (e.g. a db record change) and manual recovery than a lock timeout that might cause corruption. -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions

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

of the API races we have, and can do so with rather nice, elegant, easy to understand code, so I think the whole process has been productive whatever the H/A outcome. -- Duncan Thomas __ OpenStack Development Mailing List

Re: [openstack-dev] [cinder]Do we have plan for restoring on-line volume?

Does restoring a volume online make any logical sense? Generally operating systems don't like it when a mounted volume changes contents, and a restore, being a slow sequential write is likely to be even worse. Since you have to unmount anyway, attaching a new volume should not be an issue. Just

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

, and imthusiastic about moving forward on this for the first time in a while. Appreciated. -- Duncan Thomas On 27 July 2015 at 22:35, Gorka Eguileor gegui...@redhat.com wrote: 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

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

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

Re: [openstack-dev] [cinder]Question for availability_zone of cinder

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

Re: [openstack-dev] [cinder]Question for availability_zone of cinder

:00 Duncan Thomas duncan.tho...@gmail.com: So this has come up a few times. My question is, does having one node serving several backends really form multiple AZs? Not really, the c-vol node becomes a single point of failure. There might be value in moving the AZ setting into the per-backend

Re: [openstack-dev] [cinder] about the cinder /volumes and /volumes/detail sort APIs

The deprecated API will be removed in some future release, though the date for that is not know. It is not advised to code against a deprecated API for this reason, and any existing code that operates against a deprecated API should be updated where possible. That said, the deprecated code in

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

ot; status. > > It might be of interest to note that volume snapshots have always worked on attached volumes, and as of liberty, the backup operation now supports a --force=True option that does a backup of a live volume (via an internal snapshot, so it should be crash cons

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

ysical >> handle. >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.opensta

Re: [openstack-dev] About the response parameters of the API List volumes

e API changes > like this which are otherwise backward incompatible since you're changing > the response. > > [1] https://review.openstack.org/#/c/209917/ > > -- > > Thanks, > > Matt Riedemann > > > ______ >

Re: [openstack-dev] [cinder][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

process. Referencing the name of the CI in the commit message makes reviewer's lives easier so is worth doing. If you post a review now, again you will be in very good shape to get back in M. Hope this helps. -- Duncan Thomas On 3 November 2015 at 11:43, Eduard Matei <eduard.ma...@cloudfounders.

Re: [openstack-dev] [cinder][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

ions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- -- Duncan Thomas __ OpenStack Development Mailing List (not f

[openstack-dev] Cinder mid-cycle planning survey

Hi Folks The Cinder team is trying to plan our mid-cycle meetup again. Can anybody interested in attending please fill out this quick survey to help with planning, please? https://www.surveymonkey.com/r/Q5FZX68 Closing date is 11th November. Thanks -- -- Duncan Thomas

Re: [openstack-dev] [Cinder] New extension API for detecting cinder-backup ?

I think option 2 is the better one, and we can just call it something else other than capabilities. Available_services or similar On 16 Oct 2015 11:05, "Ramakrishna, Deepti" wrote: > Hi, > > > > We need a way to let Horizon know about the presence of cinder-backup >

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

Ah, I apologise, I missed the but where it defaults to force=true. I withdraw the objection. I've no strung feelings about the change either way, in that case. On 10 Jul 2015 10:58, Gorka Eguileor gegui...@redhat.com wrote: On Fri, Jul 10, 2015 at 10:28:06AM +0300, Duncan Thomas wrote

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

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. On 10 Jul 2015 07:33, hao wang sxmatch1...@gmail.com wrote: Cinder now doesn't check the

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

It sounds like the extra specs you configured are not selective enough. Can you post up your 3 cinder.conf files from the c-vol nodes, and the commands used to create the volume type, please? On 13 Jul 2015 08:00, Eduard Matei eduard.ma...@cloudfounders.com wrote: Hi, Forgot to mention, indeed

Re: [openstack-dev] [cinder] [nova] Cinder and Nova availability zones

Except your failure domain includes the cinder volume service, independent of the resiliency of you backend, so if they're all on one node then you don't really have availability zones. I have historically strongly espoused the same view as Ben, though there are lots of people who want fake

Re: [openstack-dev] FW: [cinder] Microsoft CI Still Disabled

e Cinder midcycle sprint, this CI was still not > ready and it hasn't been for 30 days now. > >> > >>Where are we with things, and why has communication been so poor with > the Cloud Base solutions team? > >> > >>[1] - > https://na01.safelinks.protec

Re: [openstack-dev] FW: [cinder] Microsoft CI Still Disabled

Mike is on vacation at the moment, somebody else will evaluate in his stead Hi Mike, I think the first mail was sent only on openstack-dev. We have had already over a week of reliable results on the Microsoft Cinder CI on all three jobs, we have an updated set of results available at [1]. Please

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 5 Sep 2015 05:47, "Adam Young" wrote: > Then let my Hijack: > > Policy is still broken. We need the pieces of Dynamic policy. > > I am going to call for a cross project policy discussion for the upcoming summit. Please, please, please all the projects attend. The

[openstack-dev] [Cinder] PTL Candidacy

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

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

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

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

info/openstack-dev >> >> >> >> -- >> Best Wishes For You! >> >> __________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-req

Re: [openstack-dev] [cinder] LVM snapshot performance issue -- why isn't thin provisioning the default?

On 16 Sep 2015 20:42, "yang, xing" wrote: > On 9/16/15, 1:20 PM, "Eric Harney" wrote: > >This sounds like a good idea, I'm just not sure how to structure it yet > >without creating a very confusing set of config options. > > I’m thinking we could have a

Re: [openstack-dev] [cinder] LVM snapshot performance issue -- why isn't thin provisioning the default?

any examples? I'm not sure if we can fix it without breaking people's existing configs but I think it is worth trying. I'll add it to the list of things to talk about briefly in Tokyo. -- Duncan Thomas __ OpenStack Develo

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 18 Sep 2015 05:13, "Jim Rollenhagen" wrote: > FWIW, in Ironic, we added the public_endpoint config to fix the bug > quickly, but we'd really prefer to support both that and the > secure_proxy_ssl_header option. It would use public_endpoint if it is > set, then fall

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

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 - manila is not going to suddenly start

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

I can definitely see your logic, but we've a history in cinder of vendors trying to cram drivers in at the last minute which we very much wanted to stop dead. I might suggest that the second milestone, rather than the first might be a better one to dedicate to driver reviews... An interesting

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

I think disabling it by default in early M should help shake out any remaining issues - we can decide if we actually release that way later. I'm against actually removing the V1 code however On 29 Sep 2015 15:56, "Ivan Kolodyazhny" wrote: > First of all, I would like to say

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 26 September 2015 at 07:04, Joshua Harlow wrote: > Maybe there should be a 'warm' project or something ;) > > Or we can call it 'bbs' for 'building block service' (obviously not > bulletin board system); ask said service to build a set of blocks into well > defined

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 28 September 2015 at 12:35, Sylvain Bauza wrote: > About the maintenance burden, I also consider that patching clients is far > more easier than patching an API unless I missed something. > > I think I very much disagree there - patching a central installation is much, much

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

The trouble with putting more intelligence in the clients is that there are more clients than just the one we provide, and the more smarts we require in the clients, the more divergence of functionality we're likely to see. Also, bugs and slowly percolating bug fixes. On 28 Sep 2015 11:27,

Re: [openstack-dev] [Openstack-i18n] [nova][i18n] Is there any point in using _() inpython-novaclient?

A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > > ___ > Openstack-i18n mailing list > openstack-i...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > -- -- Duncan Thomas

Re: [openstack-dev] [nova][cinder] how to handle AZ bug 1496235?

Hi I thought I was late on this thread, but looking at the time stamps, it is just something that escalated very quickly. I am honestly surprised an cross-project interaction option went from 'we don't seem to understand this' to 'deprecation merged' in 4 hours, with only a 12 hour discussion on

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

e Nova API is intending to provide. > > > >> -James >> > > __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubsc

Re: [openstack-dev] [CINDER] [PTL Candidates] Questions

able cinder to be what I and many others would like it be. I hope this helps people with their decision. Whomever wins, I have high hopes for the future, there is nobody standing who hasn't been a pleasure to work with in the past, and I don't expect that to change in the fu

<    1   2   3   4   5   >