Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

On Wed, Apr 12, 2017 at 05:27:13PM -0500, Jay S Bryant wrote: > I also didn't receive an e-mail. :-( > I don't think we need to perpetuate this thread for everybody that didn't get it. I think it's safe to see that a large number of folks have not recieved the email. (Me included) :)

Re: [openstack-dev] [tc][election] Questions for Candidates

On Wed, Apr 12, 2017 at 04:19:55PM +, Kendall Nelson wrote: > Hello Candidates! > > You all have proven yourselves to be crucial parts of the community and I > just wanted to say good luck to each one of you in the upcoming election! > > Also though, I thought it might be good to ask a few

Re: [openstack-dev] [tc] [elections] Available time and top priority

On Wed, Apr 12, 2017 at 07:05:42PM +0900, Ildiko Vancsa wrote: > > As a version of this idea, I was thinking of an #openstack-tc IRC channel, > but wanted to give it another thought before bringing it up. :) While I don’t > have the intention to necessarily increase the number of IRC channels

Re: [openstack-dev] [tc][elections]questions about one platform vision

On Wed, Apr 12, 2017 at 02:54:30AM +, joehuang wrote: > Hello, > > I heard the one platform vision in OpenStack now and then: One platform for > virtual machines, containers and bare metal. > > I also learned that there are some groups working on making Kubernets being > able to manage

Re: [openstack-dev] [tc] [elections] Available time and top priority

On Mon, Apr 10, 2017 at 03:40:30PM -0500, Matt Riedemann wrote: > > I don't attend many TC meetings, it's usually on accident, but yeah, when I > do I always note the flurry of cross-talk chatter that just drowns > everything out. I feel like there are usually at least 3 parallel > conversations

Re: [openstack-dev] [tc] [elections] Available time and top priority

On Mon, Apr 10, 2017 at 11:16:57AM +0200, Thierry Carrez wrote: > > So my question is the following: if elected, how much time do you think > you'll be able to dedicate to Technical Committee affairs (reviewing > proposed changes and pushing your own) ? Starting today, I've moved from a position

[openstack-dev] [election] [tc] TC Candidacy (smcginnis)

Hello everyone, I would like to put my name in for the TC election. For those of you that don't know me, my name is Sean McGinnis and I have been the Cinder PTL since the Mitaka release. I have been an operator, consumer, and developer of infrastructure related services since the late 90's. I

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

On Wed, Mar 29, 2017 at 10:56:41AM -0400, Brian Rosmaita wrote: > On 3/8/17 2:03 PM, Matthew Thode wrote: > > So, pycrypto upstream is dead and has been for a while, we should look > > at moving off of it for both bugfix and security reasons. > > > > Currently it's used by the following. > > > >

Re: [openstack-dev] OpenStack Bug Smash for Pike Release

I can say from my experience being involved in the last event that these can be very productive. It was great seeing a room full of devs just focused on getting bugs fixed! I highly encourage anyone interested to attend. I would also recommend cores for each project to pay some attention to

Re: [openstack-dev] [Cinder] Tags for volumes

On Mon, Mar 27, 2017 at 03:13:59PM +0800, 王玺源 wrote: > Hi cinder team: > > I want to know what's your thought about adding tags for volumes. > > Now Many resources, like Nova instances, Glance images, Neutron > networks and so on, all support tagging. And some of our cloud customers >

Re: [openstack-dev] [qa][cinder] RFC: Cinder test on Tempest

On Wed, Mar 22, 2017 at 01:08:23PM -0700, Ken'ichi Ohmichi wrote: > Hi, > > Now we need to update Tempest for following Cinder API status. > I have an idea for restructuring and happy to see feedback about that. > > Now Cinder API status is > V1: Deprecated > V2: Deprecated > V3: Current >

Re: [openstack-dev] [ironic] Translations removal

On Wed, Mar 22, 2017 at 08:42:42AM -0500, Kevin L. Mitchell wrote: > On Tue, 2017-03-21 at 22:10 +, Taryma, Joanna wrote: > > However, pep8 does not accept passing variable to translation > > functions, so this results in ‘H701 Empty localization string’ error. > > > > Possible options to

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

> > We have a very limited slots available for interested projects so it will > be a first come first served process. Let me know if you are interested and > I will reserve a slot for you if there are spots left. > I would like one for Cinder, but if we are running low on time slots I would be

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

> > > As far as I can tell: > - Cinder v1 if I'm not mistaken has been deprecated in Juno, so it's > deprecated in all supported releases. > - Glance v1 has been deprecated in Newton, so it's deprecated in all > supported releases > - Keystone v2 has been deprecated in Mitaka, so testing *must*

Re: [openstack-dev] [neutron][astara-neutron]

On Fri, Mar 10, 2017 at 09:32:15AM -0600, Dariusz Śmigiel wrote: > Hey, > astara-neutron repo seems to be broken for a long time [1]. > Last merged patches are dated on July 2016 [2]. After that, there is a > queue with jenkins -1s. It doesn't look like to be maintained anymore. > > Is there an

Re: [openstack-dev] Hitachi Data Systems drivers

On Thu, Mar 09, 2017 at 12:47:17PM -0300, José Eduardo de Carvalho Mello Junior wrote: > > Effective, Mar 9, 2017, Hitachi Data Systems will offer its drivers for > download exclusively via https://support.hds.com. Should you need > assistance with drivers, please contact >

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

On Mon, Mar 06, 2017 at 09:06:18AM -0500, Sean Dague wrote: > On 03/06/2017 08:43 AM, Andreas Jaeger wrote: > > On 2017-03-06 14:03, Sean Dague wrote: > >> I'm trying to understand the implications of > >> https://review.openstack.org/#/c/439500. And the comment in the linked > >> email: > >> >

[openstack-dev] [Cinder] PTG Recap

I leiu of a lengthy email that very few will read, this is just a pointer. Jay Bryant (jungleboyj) did a great job during the PTG of capturing notes and action items from our discussions. One of the items discussed was around improving capturing these details and making them easier to find months

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

On Mon, Feb 27, 2017 at 06:26:48PM +, Jeremy Stanley wrote: > On 2017-02-27 09:35:21 -0800 (-0800), Clint Byrum wrote: > [...] > > do you believe that the single openstack-dev mailing list is > > working fine and we should change nothing? If not, what problems > > has it created for you? >

[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] 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] Hierarchical quotas at the PTG?

On Fri, Feb 10, 2017 at 02:56:56PM -0600, Matt Riedemann wrote: > Operators want hierarchical quotas [1]. Nova doesn't have them yet and we've > been hesitant to invest scarce developer resources in them since we've heard > that the implementation for hierarchical quotas in Cinder has some issues.

Re: [openstack-dev] Mitaka - Unable to attach volume to VM

On Fri, Feb 10, 2017 at 02:18:15AM +0700, Sam Huracan wrote: > Hi guys, > > I meet this issue when deploying Mitaka. > When I attach LVM volume to VM, it keeps state "Attaching". I am also > unable to boot VM from volume. > > This is /var/log/nova/nova-compute.log in Compute node when I attach

Re: [openstack-dev] [All] IRC Mishaps

On Thu, Feb 09, 2017 at 08:43:05PM +, Chandrasekar, Dharini wrote: > My IRC mishaps go like: > > Tried to set a channel topic and ended up making it > look like messages sent on the channel instead. > Oh, there was the time I accidentally banned everyone from the Cinder channel. That was

Re: [openstack-dev] [release] Support phase clarification

> > Yup I think 6 months makes sense. I'll work up a change to the releases repo > to record the target date for switching between Phases and EOL dates. > > There will be a little duplication of data but I think we can live with that. > > Yours Tony. Perfect - thanks Tony and Jeremy! Exactly

Re: [openstack-dev] [release] Support phase clarification

On Thu, Feb 09, 2017 at 05:41:26PM +, Jeremy Stanley wrote: > On 2017-02-09 11:24:46 -0600 (-0600), Sean McGinnis wrote: > [...] > > Thanks both. The original question still stands though. Are we rolling > > over support phases at the 6 month boundary as stated, or is the i

Re: [openstack-dev] [release] Support phase clarification

On Thu, Feb 09, 2017 at 05:10:00PM +0800, ChangBo Guo wrote: > Just copy statement from > http://docs.openstack.org/project-team-guide/stable-branches.html#support-phases > > "*The exact length of any given stable branch life support is discussed > amongst stable branch maintainers and

[openstack-dev] [release] Support phase clarification

Just looking for clarification on our support phase timing now with the shorter release cycle for Ocata. According to our published support phase schedule [1], each phase is in 6 month increments from the release date. In the past, this had lined up nicely so that when N was release, N-1 and N-2

Re: [openstack-dev] [Oslo][all] Pike PTG idea & discussion

On Mon, Feb 06, 2017 at 01:48:59PM -0600, Lance Bragstad wrote: > Not sure how much time it would require at the PTG - but I'd really like to > discuss the ability to add in-code descriptions of oslo.policy objects, and > eventually whatever we need to advertise new defaults. I'm hoping this will

[openstack-dev] [Elections][PTL][Cinder] Sean McGinnis Candidacy for Pike

Hello everyone, I have been the Cinder PTL since the Mitaka release and I would love the opportunity to be the PTL one more time. I work for Dell EMC, working with storage for the last 14+ years. I am lucky enough that I have the support to focus on OpenStack for my job. I also have the support

[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

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] 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

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] 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:

Re: [openstack-dev] [all] Using \ for multiline statements

On Fri, Dec 23, 2016 at 03:00:02PM +0100, Radomir Dopieralski wrote: > There is a problem with the use of backslash at the end of the line, where > if you also put a space after it, it no longer does what it seemingly > should. Oooh. nice. This is the good technical reason I was looking for. So

Re: [openstack-dev] [all] Using \ for multiline statements

> > By the way, can we finally all agree that commit message titles need to be a > proper ('merican) English grammatically correct sentence that begins with a > capital letter and ends with a period. And flavor is flavor, it's not > flavour. > > Happy holidays. > > -- > > Thanks, > > Matt

[openstack-dev] [all] Using \ for multiline statements

Looking for input from everyone, particularly those with more in-depth Python knowledge. In Cinder for some time we have been trying to enforce using () or reformatting code to avoid using \ to have statements span multiple lines. I'm not sure when this actually started, but I think it may be one

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 <sean.mcgin...@gmx.com> > wrote: I'm using a modified version of the lastcomment script: https://github.c

[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] 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 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 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 the

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] [nova] [Openstack-operators] How to expose the compute node local disks to instances

Hi Belmiro, In Cinder there is the "raw disk device" driver that has been used by some for Hadoop and similar applications. That may be something to look at, but with a big warning. That being that it is deprecated in the Ocata release and will be removed in Pike. The reason it is going to be

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

On Wed, Dec 07, 2016 at 02:29:03PM +0100, Thierry Carrez wrote: > > So how about: > - we enable an #openstack-meeting-5 to instantly relieve scheduling pressure > - we allow teams to hold meetings in their project channel if they want > to (and show them all on the meeting agenda through the

[openstack-dev] [all] Ocata Bugsmash

Last week was the Ocata Bugsmash in Shenzhen, China. Many developers from around China gathered to debug, test, and fix a large number of bugs across many of the most popular projects. I wanted to take an opportunity to thank Huawei, Intel, and everyone involved for making this event happen. It

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

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

Re: [openstack-dev] [new][nimble] New project: Nimble

On Fri, Nov 25, 2016 at 05:41:28PM +0800, Zhenguo Niu wrote: > hi all, > > We are pleased to introduce Nimble, a new OpenStack project which aims to > provide bare metal computing management. Has this name been cleared for use? Nimble is the name of a company, so like Quantum, this seems to me

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

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

Re: [openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'

On Wed, Nov 16, 2016 at 04:04:52PM +, Brian Rosmaita wrote: > Hello Translators, > > We're having a discussion about a new image "visibility" value for Glance, > and before we go too far, it would be helpful to know whether what we're > worried about is going to matter for ESL people. > >

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

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

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On Tue, Nov 01, 2016 at 03:47:11PM +, Jeremy Stanley wrote: > On 2016-10-31 13:23:48 -0500 (-0500), Sean McGinnis wrote: > > Last Tuesday we had a cross-project session around the use of > > proprietary code/libs/binaries in OpenStack drivers. The challenge > > we are

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On Tue, Nov 01, 2016 at 12:26:11AM -0400, Ben Swartzlander wrote: > On 10/31/2016 02:23 PM, Sean McGinnis wrote: > >Last Tuesday we had a cross-project session around the use of proprietary > >code/libs/binaries in OpenStack drivers. The challenge we are running into > >is w

[openstack-dev] [All] Cross project prorietary driver code recap

Last Tuesday we had a cross-project session around the use of proprietary code/libs/binaries in OpenStack drivers. The challenge we are running into is where to draw the line with these drivers. What is the appropriate policy to have in place to allow/disallow certain approaches. There was a lot

Re: [openstack-dev] [nova] Ocata release schedule

On Mon, Oct 31, 2016 at 08:56:43AM -0500, Matt Riedemann wrote: > I plan on posting some recaps of the design summit sessions, but I > wanted to quickly get out the Ocata release schedule for Nova. > That's in the wiki here: > >

[openstack-dev] [Cinder] Proposed logo

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

Re: [openstack-dev] [nova][cinder] Addressing mangled LUKS passphrases (bug#1633518)

On Fri, Oct 21, 2016 at 12:07:08PM +0100, Lee Yarwood wrote: > Hello, > > I documented bug#1633518 [1] last week in which volumes encrypted prior > to Ib563b0ea [2] used a slightly mangled passphrase instead of the > original passphrase provided by the configured key manager. > > My first

[openstack-dev] [Cinder] No weekly meeting

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

[openstack-dev] [Doc] Inclusion of microversion API support in CLI reference

Just getting this out there to either get educated or to start a conversation... While going through some of the DocImpact generated bugs for python-cinderclient I noticed a few that added new parameters to existing CLI commands. As Cinder has now moved to using microversions for all API changes,

Re: [openstack-dev] [all][stable] Moving stable/mitaka to Phase-II and liberty to Phase-III

On Tue, Oct 11, 2016 at 08:34:12AM +1100, Tony Breeds wrote: > On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote: > > > I think it would also make sense to *release* on the boundary of the switch; > > so that it’s clear which phase a release followed. > > I agree, I don't really

Re: [openstack-dev] [QA][Cinder]Removing Cinder v1 in Tempest

On Mon, Oct 10, 2016 at 03:47:39PM +0300, Duncan Thomas wrote: > If we can get them running on cinder patches via a different job, then > removing them from the common job afterwards seems reasonable. > > There's no strong will to remove them, several libraries still use them, > and given we're

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

On Mon, Oct 10, 2016 at 08:37:53AM -0400, Doug Hellmann wrote: > > > > We had a lot of feedback that the unstructured discussion time from > the Friday "meetups" at the summits were the most productive time > for teams, but I'm sure there are quite a few cases like what you > describe. Maybe the

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

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

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

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

Re: [openstack-dev] [all][elections][TC] TC candidacy

On Mon, Oct 03, 2016 at 10:53:30AM -0700, John Dickinson wrote: > > > On 27 Sep 2016, at 9:21, Sean McGinnis wrote: > > > I would like to announce my candidacy for a position on the Technical > > Committee. > > > > > Sean, > > Are there some spe

Re: [openstack-dev] [tc] open question to the candidates

On Mon, Oct 03, 2016 at 03:30:56PM +, gordon chung wrote: > > > the TC has historically been a reactive council that lets others ask for > change and acts as the final approver. do you believe the TC should be a > proactive committee that initiates change and if yes, to what scope? > more

[openstack-dev] [all][elections][TC] TC candidacy

complexity anywhere it's possible and where it makes sense. It would be an honor to serve as a member of the TC and help do whatever I can to help the community continue to succeed and grow. Thank you for your consideration. Sean McGinnis (smcginnis

Re: [openstack-dev] [ptl] code churn and questionable changes

On Wed, Sep 21, 2016 at 12:43:06PM +, Dolph Mathews wrote: > > > > And as a general rule, there is zero benefit to filing bugs in Launchpad if > there is no end-user impact (especially against 20+ projects). Close the > bug as Opinion (if Launchpad hasn't already broken) and focus on the >

Re: [openstack-dev] [openstack-ansible] cinder volume lxc and iscsi

On Wed, Sep 14, 2016 at 05:08:51PM +0200, Fabrice Grelaud wrote: > Hi, > > i need recommendations to setup block storage with dell storage center > iscsi drivers. > > As seen in doc > (http://docs.openstack.org/developer/openstack-ansible/mitaka/install-guide/configure-cinder.html), > no need

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > > > Lastly, election officials are also reachable through the > > #openstack-election Freenode channel. > > I wonder if it's worth having all conversations in

[openstack-dev] [Cinder] PTL candidacy

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

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

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

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On Wed, Sep 07, 2016 at 01:07:22PM -0400, Sean Dague wrote: > On 09/07/2016 12:27 PM, Thierry Carrez wrote: > > Barrett, Carol L wrote: > >> From: Sean Dague [mailto:s...@dague.net] > >>> I think another option would be to run the PTL election early, but just > >>> don't have the turn over

Re: [openstack-dev] [release] proposing adding Tony Breeds to "Release Managers" team

On Tue, Sep 06, 2016 at 07:37:55PM -0400, Emilien Macchi wrote: > My vote doesn't count but I still have feedback to share. > > As a PTL I have to release multiple projects and Tony was always very > helpful and responsive in the reviews. > I would be super happy to have him part of release

Re: [openstack-dev] [Cinder] The State of the NFS Driver ...

Thanks for the write up Jay. This is useful. Added [Cinder] tag to subject line... On Tue, Aug 30, 2016 at 10:50:38AM -0500, Jay S. Bryant wrote: > All, > > I wanted to follow up on the e-mail thread [1] on Cloning support in > the NFS driver. The purpose of this e-mail is to provide the plan

Re: [openstack-dev] [release][barbican][cinder][cloudkitty][ironic][magnum][monasca][searchlight][senlin][solum][swift][tripleo][watcher][winstackers] tags needed to be considered part of Newton

On Mon, Aug 29, 2016 at 10:50:27AM -0400, Doug Hellmann wrote: > We have several projects using the cycle-with-intermediary release > model for which we have not had any releases yet this cycle. Please > consider a release this week, and be aware that we need a release > by the final deadline in

Re: [openstack-dev] [Nova] Support specified volume_type when boot instance, do we like it?

On Mon, Aug 29, 2016 at 09:29:57AM -0400, Andrew Laski wrote: > > > > On Mon, Aug 29, 2016, at 09:06 AM, Jordan Pittier wrote: > > > > > > On Mon, Aug 29, 2016 at 8:50 AM, Zhenyu Zheng > > wrote: > >> Hi, all > >> > >> Currently we have customer demands about adding

Re: [openstack-dev] [OpenStack-docs] [cinder] [api] [doc] API status report

On Sat, Aug 27, 2016 at 07:46:48PM +0200, Andreas Jaeger wrote: > On 08/26/2016 11:33 PM, Anne Gentle wrote: > > Hi cinder block storage peeps: > > > > I haven't heard from you on your comfort level with publishing so I went > > ahead and made the publishing job myself with this review: > > > >

Re: [openstack-dev] [gate] [cinder] A current major cause for gate failure - cinder backups

On Wed, Aug 24, 2016 at 07:24:54AM +, Li, Xiaoyan wrote: > Hi, > > I noticed that as VolumesBackupsV1Test and VolumesBackupsV2Test use same > volume to do backup creation test etc. > When creating backup from volume, it needs to attach volume. As both two > tests use same volume, they

[openstack-dev] [Cinder] Design Summit Space Needs

Hey team, I need to let folks know what we would like for rooms in Barcelona. This is always the tricky part of guesstimating what we will need by then. I'll bring this up in next week's meeting to discuss, but I wanted to get it out there so everyone could start thinking about it now. In Austin

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

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

Re: [openstack-dev] [ThirdParty][CI] DSS Cinder CI <budik...@list.ru> spam

On Thu, Aug 18, 2016 at 07:57:25AM -0700, Elizabeth K. Joseph wrote: > On Thu, Aug 18, 2016 at 7:30 AM, Elizabeth K. Joseph > wrote: > > On Thu, Aug 18, 2016 at 7:14 AM, Jesse Pretorius > > wrote: > >> Hi everyone, > >> > >> Today we

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

On Sat, Aug 13, 2016 at 08:04:13PM -0700, Joshua Harlow wrote: > Sean McGinnis wrote: > >On Fri, Aug 12, 2016 at 05:55:47AM -0400, Sean Dague wrote: > >>A devstack patch was pushed earlier this cycle around os-brick - > >>https://review.openstack.org/341744 > >&

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

On Fri, Aug 12, 2016 at 03:40:47PM +0300, Duncan Thomas wrote: > On 12 Aug 2016 15:28, "Thierry Carrez" wrote: > > > > Duncan Thomas wrote: > > > I agree that leaving broken drivers in tree is not significantly better > > from an operational perspective. But I think the

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

On Fri, Aug 12, 2016 at 05:55:47AM -0400, Sean Dague wrote: > A devstack patch was pushed earlier this cycle around os-brick - > https://review.openstack.org/341744 > > Apparently there are some os-brick operations that are only safe if the > nova and cinder lock paths are set to be the same

Re: [openstack-dev] [cinder] [neutron] [ironic] [api] [doc] API status report

> > Sorry, in reviewing further today I found another project that does not > have a publish job but has in-tree source files: > > cinder > > Team cinder: can you let me know where you are in your publishing comfort > level? Please add an api-ref-jobs: line with a target of block-storage > to

Re: [openstack-dev] [tc][cinder] tag:follows-standard-deprecation should be removed

> >> > >> As follow up on the mailing list discussion [0], gerrit activity > >> [1][2] and cinder 3rd party CI policy [3] I'd like to initiate > >> discussion how Cinder follows, or rather does not follow, the standard > >> deprecation policy [4] as the project has been tagged on the assert > >>

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

On Wed, Aug 10, 2016 at 11:26:28PM +0200, Nicolas Trangez wrote: > Sean and team, > > Sadly enough, we have been unable to resolve the recent issues in the > system/lab backing our CI server (originally caused by some hardware > migrations), and it's unclear when this would be back in a stable >

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

. > > Mike, you must have left the midcycle by the time this topic came > up. On the issue of out-of-tree drivers, I specifically offered this > proposal (a community managed mechanism for distributing driver > bugfix backports) as an compromise alternative to try to address the > needs of both

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Tue, Aug 09, 2016 at 03:56:57PM -0700, Mike Perez wrote: > If you want to change that, work with the stable team on the various options > provided. This tangent of people whining on the mailing list and in > #openstack-cinder is not going to accomplish anything. That's what we're doing here

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

> > Unless you manage to get it approved for the global policy, I think > you will effectively make your stable:follows-policy tag obsolete, > and then it should be removed from your project. Read the > requirements: > >

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Sat, Aug 06, 2016 at 08:00:06PM -0400, Ben Swartzlander wrote: > On 08/06/2016 06:11 PM, Jeremy Stanley wrote: > >On 2016-08-06 17:51:02 -0400 (-0400), Ben Swartzlander wrote: > >[...] > >>when it's no longer to run dsvm jobs on them (because those jobs > >>WILL eventually break as infra stops

<    1   2   3   4   5   6   7   >