Re: [openstack-dev] [cinder] Create backup with snapshots

From: 王玺源 [wangxiyuan1...@gmail.com] Sent: Thursday, March 2, 2017 10:21 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [cinder] Create backup with snapshots Hi cinder team: We met a problem about backup create

[openstack-dev] [cinder] Create backup with snapshots

Hi cinder team: We met a problem about backup create recently. The backup can be created from volumes or snapshots. In the both cases, the volume' s status is set to 'backing-up'. But as I know, when users create backup with snapshots, the volume is not used(Correct me if I'm wrong). So why the

[openstack-dev] [Cinder] Team photo at PTG

Hey team! They are giving all teams the opportunity to get a team photo taken at the PTG. I've signed us up for 9:30am on Thursday. Please take your weekly shower and join us on the third floor in front of the grand ballroom. Sean

[openstack-dev] [cinder] Heirarchical Quota Implementation Issues

Hi All, It is heard that Cinder faced some issues while implementing hierarchical quotas.I would be nice if somebody from Cinder team can share the issues , as it will be useful for the PTG next week.

[openstack-dev] [cinder] cinder 10.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for cinder for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [Cinder] Project mascot available

On Tue, Feb 14, 2017 at 2:24 PM, Walter Boring wrote: > How does Horse translate to Cinder block? > I don't get it. Our original Cinder block made a lot of sense, > considering the name of the project. > > > Horses uses horseshoes, which were created due the needs of the

Re: [openstack-dev] [Cinder] Project mascot available

On 2/14/2017 5:28 PM, Mike Perez wrote: On 08:24 Feb 14, Walter Boring wrote: How does Horse translate to Cinder block? I don't get it. Our original Cinder block made a lot of sense, considering the name of the project. This is...just an odd horse for no particular reason. As I remember

Re: [openstack-dev] [Cinder] Project mascot available

On 08:24 Feb 14, Walter Boring wrote: > How does Horse translate to Cinder block? > I don't get it. Our original Cinder block made a lot of sense, considering > the name of the project. > > > This is...just an odd horse for no particular reason. As I remember from the midcycle meetup

Re: [openstack-dev] [Cinder] Project mascot available

How does Horse translate to Cinder block? I don't get it. Our original Cinder block made a lot of sense, considering the name of the project. This is...just an odd horse for no particular reason. On Mon, Feb 13, 2017 at 6:43 PM, Sean McGinnis wrote: > For your

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

On 2/14/2017 8:48 AM, Matt Riedemann wrote: OK so the NFS job would tickle it, but that might not be in the experimental queue for devstack (but it is in nova's experimental queue so we could hack this up to test it). I thought we were testing volume retype/migration now though? That calls

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

On 2/14/2017 7:48 AM, Duncan Thomas wrote: This is only used by the file based drivers, who need to call nova for assistance with attached snapshots. Most drivers won't use it, including the default, LVM. I can't comment on the test coverage, sorry. On 14 February 2017 at 13:01, Sean Dague

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

This is only used by the file based drivers, who need to call nova for assistance with attached snapshots. Most drivers won't use it, including the default, LVM. I can't comment on the test coverage, sorry. On 14 February 2017 at 13:01, Sean Dague wrote: > After some of the

[openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

After some of the confusion around endpoints in devstack, we decided to simplify the endpoints registered in devstack to only the ones needed for development. Basically only register "public" interfaces unless there is something special about the service. https://review.openstack.org/#/c/433272/

[openstack-dev] [Cinder] Project mascot available

For your viewing and slide designing pleasure... We have the official mascot completed from the illustrators. Multiple formats are available from here: https://www.dropbox.com/sh/8s3859c6qulu1m3/AABu_rIyuBM_bZmfGkagUXhua?dl=0 Stay golden, pony boy. Sean

Re: [openstack-dev] [cinder] cinder 10.0.0.0rc1 (ocata)

Hi, With Cinder master being open for Pike development I ask not to merge any changes with DB schema migrations before sanity check migration [1] gets in. It's supposed to block going forward until all of the Ocata's data migrations were executed and should be the first migration in Pike. [1] 

[openstack-dev] [cinder] cinder 10.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for cinder for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

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

Hello! > > > __ > > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >

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

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

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 os-vol-host-attr:host like hostname#RBD, cinder

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

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

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

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

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 (called "storage node"). On the

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

Hi All, According to the results of our Doodle poll, the new meeting day will be __Thursday__ starting from next week. The time slot and the meeting channel are supposed to remain the same, I hope the patch [1] to register the changes gets merged soon to make it fully official. In this sense,

[openstack-dev] [cinder] High load with oflag=direct

Hi, I'm using cinder with lvm (mitaka release). Actually all works well, but I noticed that when I create a new bootable volume from an image, the storage backend has an intensive cpu/disk usage with a load around 12. I think this happens because cinder use dd with oflag=direct during the copy. I

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

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

On 01/23/2017 11:29 AM, Marco Marino wrote: At the moment I have: volume_clear=zero volume_clear_size=30 <-- MBR will be deleted here! with tick provisioning I think this can be a good solution in my case. Let me know what do you think about this. If security is not a concern then that's fine.

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

At the moment I have: volume_clear=zero volume_clear_size=30 <-- MBR will be deleted here! with tick provisioning I think this can be a good solution in my case. Let me know what do you think about this. Thank you Marco 2017-01-23 17:21 GMT+01:00 Chris Friesen : >

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

On 01/21/2017 03:00 AM, Marco Marino wrote: Really thank you!! It's difficult for me find help on cinder and I think this is the right place! @Duncan, if my goal is to speeding up bootable volume creation, I can avoid to use thin provisioning. I can use image cache and in this way the "retrieve

Re: [openstack-dev] [cinder]Can we run cinder-volume and cinder-backup on a same host?

Hi Michal, Thank you for explaining! I could understand the mechanism of cinder-backup. If you're able to reproduce a scenario that fails these assumptions, please file a bug report and we'll be happy to investigate and provide a fix. Sure. But, according to your explanation, my assumptions

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

Really thank you!! It's difficult for me find help on cinder and I think this is the right place! @Duncan, if my goal is to speeding up bootable volume creation, I can avoid to use thin provisioning. I can use image cache and in this way the "retrieve from glance" and the "qemu-img convert to RAW"

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

There's also cinder functionality called the 'generic image cache' that does this for you; see the (per-backend) config options: image_volume_cache_enabled, image_volume_cache_max_size_gb and image_volume_cache_max_count On 20 January 2017 at 16:54, Chris Friesen

Re: [openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

On 01/20/2017 04:07 AM, Marco Marino wrote: Hi, I'm trying to use cinder with lvm thin provisioning. It works well and I'd like to know if there is some reason lvm thin should be avoided in mitaka release. I'm trying to use with max_over_subscription_ratio = 1.0 so I don't have problems with

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

[openstack-dev] [cinder] dog command in Sheepdog is executable, not library

Hi, I've confirmed the commit "Mark the sheepdog driver as unsupported" [1]. Sorry for CI failure. The problem will be fixed by Sheepdog team soon. I have an opinion about license. AFAIU, except CI failure, the reason why the Sheepdog driver was marked is that "dog", Sheepdog admin command

[openstack-dev] [cinder] Can I use lvm thin provisioning in mitaka?

Hi, I'm trying to use cinder with lvm thin provisioning. It works well and I'd like to know if there is some reason lvm thin should be avoided in mitaka release. I'm trying to use with max_over_subscription_ratio = 1.0 so I don't have problems with over subscription. I using thin provisioning

Re: [openstack-dev] [cinder]Can we run cinder-volume and cinder-backup on a same host?

On Fri, 2017-01-20 at 14:15 +0900, Rikimaru Honjo wrote: > Hi Cinder devs, > > I have a question about cinder. > Can I run cinder-volume and cinder-backup on a same host when I using > iscsi backend? > > I afraid that iscsi operations will be conflicted between cinder- > volume and

[openstack-dev] [cinder]Can we run cinder-volume and cinder-backup on a same host?

Hi Cinder devs, I have a question about cinder. Can I run cinder-volume and cinder-backup on a same host when I using iscsi backend? I afraid that iscsi operations will be conflicted between cinder-volume and cinder-backup. In my understanding, iscsi operations are serialized for each

[openstack-dev] [cinder] "Snapshot-manage imports snapshots with wrong size"

Hi, folks. Having worked on this bug [0] I could reproduce it with lvm as a backend. And during it further investigation, I found the real problem that triggers it. Here [1] after getting the real snapshot size, we are trying to update 'size' column. But actually snapshot's size is stored in

Re: [openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs

Thanks for giving this review Michal. On Thu, Jan 19, 2017 at 8:29 AM, Andreas Jaeger wrote: > On 2017-01-19 11:10, Michal Dulko wrote: > > Hi all, > > > > I've seen some confusion around new Cinder CI jobs being proposed to > > project-config in yesterday's IRC scrollback. This

Re: [openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs

On 2017-01-19 11:10, Michal Dulko wrote: > Hi all, > > I've seen some confusion around new Cinder CI jobs being proposed to > project-config in yesterday's IRC scrollback. This email aims to sum > this up and explain purposes of what's being proposed. Thanks a lot, Michal! That helps me seeing

[openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs

Hi all, I've seen some confusion around new Cinder CI jobs being proposed to project-config in yesterday's IRC scrollback. This email aims to sum this up and explain purposes of what's being proposed. Background == For a few releases we're aiming to increase our functional and

Re: [openstack-dev] [cinder] Problem with lvm thin provisioning and snapshots

Ok, problem solved (it seems) in /etc/lvm/lvm.conf I need to set auto_set_activation_skip = 0 and, in my case, I set the same in /etc/cinder/lvm.conf (because I'm using a cluster configuration for lvm) Thank you 2017-01-18 16:38 GMT+01:00 Marco Marino : > Hi, I'm trying

[openstack-dev] [cinder] Problem with lvm thin provisioning and snapshots

Hi, I'm trying to use lvm thin provisioning with openstack cinder (mitaka) but I have a problem with snapshots. I'm trying to create a snapshot from a volume (detached) and then create a new volume from the snapshot. 1) Snapshot creation works well and I have (with lvs) LV

[openstack-dev] [Cinder] Ocata Priority Sprint

Just to raise awareness - we've discussed this in channel and in the weekly meeting. Today and tomorrow we will be doing a short sprint to focus on getting the Active/Active HA and new Attach/Detach API work reviewed and merged. Lists of patches for both efforts can be found in our review

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

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

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

On Mon, Jan 16, 2017 at 08:52:34AM +0100, Silvan Kaiser wrote: > Apoorva, Sean, > after some time i managed to bring up Quobyte CI last friday which tested > fine [1,2,3] for a short time and then ran into the same issues with > manage_snapshot > related tempest tests Apoorva describes (Starting

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

Regarding the reason for the failing tests: Looks like [1] switches the default for support of managed snapshots to true in devstack. As the default on that was 'false' until friday Quobyte CI did not set that option previously. I'm running tests with a revised config now. Btw, feel free to

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

Apoorva, Sean, after some time i managed to bring up Quobyte CI last friday which tested fine [1,2,3] for a short time and then ran into the same issues with manage_snapshot related tempest tests Apoorva describes (Starting chronologically at [4]). >From here i see two steps: a) look into the

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

Sean, We have resolved issues related to our CI infra[1][2]. At this point manage_snapshot related tempest tests (2) are failing, but Tintri driver does not support manage/unmanage snapshot functionalities. Could you please assist me on how to skip these tests? We are using sos-ci for our CI

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

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

Re: [openstack-dev] [cinder] Cinder replication for multisite openstack clouds

I'm thinking about disaster recovery options. Permanent data of application which needs that feature, will be put on replicated volume. On the secondary site the same applicatin will run on idle state. After switchover, replicated volume will be attached to app on secondary site, before going to

Re: [openstack-dev] [cinder] Cinder replication for multisite openstack clouds

Kemo, The next phase of development for replication is to enable replication of groups of volumes [1]. I remember, in the past, there being discussion around how we handle replication across multiple data centers and don't know that we came to a conclusion. I think we would need to better

[openstack-dev] [cinder] Cinder replication for multisite openstack clouds

HI! I've been playing with dual site openstack clouds. I use ceph as a backend for Cinder volumes. Each openstack has its own ceph cluster. Data replication is done by ceph rbd mirroring. Current Cinder replication design (cheesecake) only protects against storage failure. What about support for

Re: [openstack-dev] [cinder] Deprecate Cinder Linux SMB driver

On Wed, Jan 11, 2017 at 05:28:16PM +, Lucian Petrut wrote: > Hi, > > We're planning to deprecate the Cinder Linux SMB driver. We're taking > this decision mostly because of its limitations and lack of demand, > unlike the Windows SMB driver which is largely adopted and the current > to-go

[openstack-dev] [cinder] Deprecate Cinder Linux SMB driver

Hi, We're planning to deprecate the Cinder Linux SMB driver. We're taking this decision mostly because of its limitations and lack of demand, unlike the Windows SMB driver which is largely adopted and the current to-go Cinder driver in Hyper-V deployments. We're going to mark it as

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

Jeremy Stanley wrote: > On 2017-01-10 09:44:06 -0600 (-0600), Sean McGinnis wrote: > [...] >> It doesn't look like much has changed here. There has been one commit >> that only slightly modified the new license: [1] >> >> IANAL, and I don't want to make assumption on what can and can't be >> done,

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

. Thanks, Xing From: yang, xing Sent: Thursday, November 3, 2016 11:33 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [cinder] generic volume groups and consistency groups Hi everyone, Generic volume groups

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

On 2017-01-10 09:44:06 -0600 (-0600), Sean McGinnis wrote: [...] > It doesn't look like much has changed here. There has been one commit > that only slightly modified the new license: [1] > > IANAL, and I don't want to make assumption on what can and can't be > done, so looking to other more

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

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

[openstack-dev] [cinder] PTG planning etherpad

Hi, PTG planning etherpad wasn't advertised on the list, so I'm linking it below. It's still pretty empty, so I guess it's time to start filling it up. https://etherpad.openstack.org/p/ATL-cinder-ptg-planning Thanks, Michal

[openstack-dev] [Cinder] Reminder - no meeting this week

Just a friendly reminder that there will be no Cinder meeting this week. Regular weekly meetings will resume in January. Thanks! Sean (smcginnis) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Cinder] Refactor reset-status command for cinder resources at client side

Hi cinder members, Eharney recently add a comment about 'resource-reset-status' command here [1] on Dec 22, and I'd like to paste his comment here to get more attention and discussion before the patch can go on. *I'd like to discuss the general design here and get input from others

Re: [openstack-dev] [Cinder] Does cinder use novaclient?

Hi Jane, there is also some other uses, I know. In migration[1] when Cinder needs to migrate an attached volume, in some remotefs drivers [2], when Cinder needs to take a snapshot of an attached volume. Both seems to work fine with me. [1] http://bit.ly/2i6m1Pb [2] http://bit.ly/2i6m3GM On

Re: [openstack-dev] [Cinder] Does cinder use novaclient?

On Tue, 2016-12-20 at 14:44 +0800, lij...@gohighsec.com wrote: > Hi Cinder community, > > Does cinder use novaclient? What's the use of cinder/compute/nova.py? > > I find that there seems to have some problems when construct > novaclient in the file  cinder/compute/nova.py, >  but I think the

[openstack-dev] [Cinder] Does cinder use novaclient?

Hi Cinder community, Does cinder use novaclient? What's the use of cinder/compute/nova.py? I find that there seems to have some problems when construct novaclient in the file cinder/compute/nova.py, but I think the file is not being used. Would you explain the use of this file or how does

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

Hmm, nice! Thanks! On Mon, Dec 19, 2016 at 11:48 AM, Sean McGinnis wrote: > On Mon, Dec 19, 2016 at 08:27:52AM -0200, Erlon Cruz wrote: > > Hi Sean, what is the command to generate this output? > > > > On Fri, Dec 16, 2016 at 6:27 PM, Sean McGinnis

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

On Mon, Dec 19, 2016 at 08:27:52AM -0200, Erlon Cruz wrote: > Hi Sean, what is the command to generate this output? > > On Fri, Dec 16, 2016 at 6:27 PM, Sean McGinnis > wrote: I'm using a modified version of the lastcomment script:

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

Hi Sean, what is the command to generate this output? On Fri, Dec 16, 2016 at 6:27 PM, Sean McGinnis wrote: > Checking name: CloudByte CI > last seen: 2016-09-27 11:49:45 (80 days, 5:38:50 old) > last success: 2016-09-27 11:49:45 (80 days, 5:38:30 old) > success rate: 72%

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

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

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

Checking name: Tintri CI last seen: 2016-12-16 16:50:50 (0:43:36 old) last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old) success rate: 19% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved if the issue is not

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

Checking name: Synology DSM CI last seen: 2016-12-16 06:37:25 (10:56:44 old) last success: 2016-11-23 21:51:22 (22 days, 19:36:53 old) success rate: 52% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved if the issue is not

[openstack-dev] [Cinder] Marking Quobyte driver unsupported

Checking name: Quobyte CI last seen: 2016-11-18 08:23:05 (28 days, 9:10:41 old) last success: 2016-11-18 08:23:05 (28 days, 9:05:10 old) success rate: 35% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved if the issue is

[openstack-dev] [Cinder] Marking NexentaEdge driver unsupported

Checking name: Nexenta Edge CI last seen: 2016-12-16 17:24:40 (0:08:08 old) last success: 2016-11-23 10:54:16 (23 days, 6:33:59 old) success rate: 34% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved if the issue is not

[openstack-dev] [Cinder] Marking HPE XP driver as unsupported

Checking name: XP Cinder CI last seen: 2016-08-16 09:34:42 (122 days, 7:56:25 old) last success: 2016-08-09 14:39:13 (129 days, 2:49:02 old) success rate: 32% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved if the issue

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

Checking name: Huawei FusionStorage CI last seen: 2016-09-30 08:36:22 (77 days, 8:53:56 old) last success: 2016-09-30 08:36:22 (77 days, 8:51:53 old) success rate: 54% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved if

[openstack-dev] [Cinder] Marking DotHill drivers as unsupported

Checking name: Vedams DotHillDriver CI last seen: 2016-02-20 02:24:48 (300 days, 15:04:30 old) last success: 2016-02-17 20:46:49 (302 days, 20:41:26 old) success rate: 83% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved

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

Checking name: CloudByte CI last seen: 2016-09-27 11:49:45 (80 days, 5:38:50 old) last success: 2016-09-27 11:49:45 (80 days, 5:38:30 old) success rate: 72% Per Cinder's non-compliance policy [1] this patch [2] marks the driver as unsupported and deprecated and it will be approved if the issue

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

On 12/12/16 10:13 PM, Li, Xiaoyan wrote: > The new notification reports kinds of capacity information, includes total, > free, allocated, provisioned, visual_free. that's cool. just for reference, you can easily add support to generate metrics from this by editing the meters.yaml file[1].

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

Jeremy Stanley wrote: > On 2016-12-12 16:44:53 + (+), Duncan Thomas wrote: > [...] >> Having read the Openstack rules linked to earlier in the thread >> ( https://governance.openstack.org/tc/reference/licensing.html ) >> we're clearly violating that. > [...] > > Keep in mind that those

Re: [openstack-dev] [cinder] pending review

Hi Sam, Thank you for reporting the bug and trying to fix it. Sorry that you change sit there for such long time. I've left some comment in your patch. On Tue, Dec 13, 2016 at 12:33 PM, Sam Morrison wrote: > Hi Cinder devs, > > I’ve had a review [1] waiting for some eyes

[openstack-dev] [cinder] pending review

Hi Cinder devs, I’ve had a review [1] waiting for some eyes for over a month now. What’s the process here, usually I get a response to a review in other projects in a day or two. Is there someone I need to alert or add to the review specifically for cinder patches? Thanks, Sam [1]

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

ct: Re: [openstack-dev] [cinder] [ceilometer] On Thu, Dec 08 2016, Jiong Liu wrote: Hi Jeremy, If I'm not mistaken, there's a new pollster in Ocata that uses the Cinder API to get the metrics now, so I think the volume usage audit is getting useless. > Hello Cinder/Ceilometer community, > > &

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

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

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

On 2016-12-12 16:44:53 + (+), Duncan Thomas wrote: [...] > Having read the Openstack rules linked to earlier in the thread > ( https://governance.openstack.org/tc/reference/licensing.html ) > we're clearly violating that. [...] Keep in mind that those guidelines were drafted in

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

Agreed. Just saying that if the software is important to the community, but the distribution/licensing terms are not, there's always a solution. That's all I was trying to get at. If, however, resources don't avail themselves, that can also be indicative that the need vs issue isn't overwhelming.

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

On 12 December 2016 at 16:35, Ash wrote: > I tend to agree with you, Sean. Also, if there's a concern that some > project has changed its license, then just create a fork. In the case of > this previously GPL code, it will at least be re-distributable. In the end, > I

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

On 12 December 2016 at 16:14, Sean McGinnis wrote: > > Honestly, my opinion is it's just fine as it is, and the fact that this > license has changed doesn't make any difference. > > For most external storage there is _something_ that the deployer needs > to do outside of

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

I tend to agree with you, Sean. Also, if there's a concern that some project has changed its license, then just create a fork. In the case of this previously GPL code, it will at least be re-distributable. In the end, I just don't think this is a huge issue that cannot be easily managed. On Mon,

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

On Mon, Dec 12, 2016 at 03:07:23PM +, Duncan Thomas wrote: > On 12 December 2016 at 14:55, Andreas Jaeger wrote: > > > > > So, what are the steps forward here? Requiring a non-free library like > > drbdmanage is not acceptable AFAIU, > > > > This is pretty much where things

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

On 12 December 2016 at 14:55, Andreas Jaeger wrote: > > So, what are the steps forward here? Requiring a non-free library like > drbdmanage is not acceptable AFAIU, > This is pretty much where things went dead at the summit - there were various degrees of unacceptability (I was

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

On 2016-12-12 15:46, Sean McGinnis wrote: > On Mon, Dec 12, 2016 at 11:00:41AM +, Duncan Thomas wrote: >> It's a soft dependency, like most of the vendor specific dependencies - you >> only need them if you're using a specific backend. We've loads of them in >> cinder, under a whole bunch of

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

On Mon, Dec 12, 2016 at 08:46:55AM -0600, Sean McGinnis wrote: > On Mon, Dec 12, 2016 at 11:00:41AM +, Duncan Thomas wrote: > > It's a soft dependency, like most of the vendor specific dependencies - you > > only need them if you're using a specific backend. We've loads of them in > > cinder,

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

On Mon, Dec 12, 2016 at 11:00:41AM +, Duncan Thomas wrote: > It's a soft dependency, like most of the vendor specific dependencies - you > only need them if you're using a specific backend. We've loads of them in > cinder, under a whole bunch of licenses. There was a summit session >

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

On Mon, Dec 12, 2016 at 11:00:41AM +, Duncan Thomas wrote: It's a soft dependency, like most of the vendor specific dependencies - you only need them if you're using a specific backend. We've loads of them in cinder, under a whole bunch of licenses. There was a summit session discussing it

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

It's a soft dependency, like most of the vendor specific dependencies - you only need them if you're using a specific backend. We've loads of them in cinder, under a whole bunch of licenses. There was a summit session discussing it that didn't come to any firm conclusions. On 12 December 2016 at

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

On Mon, Dec 12, 2016 at 11:52:50AM +0100, Thierry Carrez wrote: That said, it doesn't seem to be listed as a Cinder requirement right now ? Is it a new dependency being considered, or is it currently flying under the radar ? I think this is because this library is not available on Pypi. --

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

On 2016-12-12 11:52, Thierry Carrez wrote: > Mehdi Abaakouk wrote: >> I have recently seen that drbdmanage python library is no more GPL2 but >> need a end user license agreement [1]. >> Is this compatible with the driver policy of Cinder ? > > It's not acceptable as a dependency of an OpenStack

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