During the June 11 #openstack-cinder meeting we discussed a mid-cycle meetup.
The agenda is To be Determined.
I have inquired and HP in Fort Collins, CO has room and network connectivity
available. There were some dates that worked well for reserving a nice room:
July 14,15,17,18, 21-25, 27-Aug
questions)
Subject: Re: [openstack-dev] [Cinder] Mid-cycle meetup for Cinder devs
On Thu, Jun 12, 2014 at 3:58 PM, John Griffith
john.griff...@solidfire.commailto:john.griff...@solidfire.com wrote:
On Wed, Jun 11, 2014 at 3:16 PM, D'Angelo, Scott
scott.dang...@hp.commailto:scott.dang...@hp.com
Congratulations Xing!
-Original Message-
From: yang, xing [mailto:xing.y...@emc.com]
Sent: Tuesday, June 17, 2014 10:11 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Manila] Welcome Xing Yang to the Manila core team!
Thanks Ben! It's
A Cinder blueprint has been submitted to allow the python-cinderclient to
involve the back end storage driver in resetting the state of a cinder volume:
https://blueprints.launchpad.net/cinder/+spec/reset-state-with-driver
and the spec:
https://review.openstack.org/#/c/134366
This blueprint
Thanks to everyone who commented on the spec to change reset-state to involve
the driver: https://review.openstack.org/#/c/134366/
I've put some comments in reply, and I'm going to attempt to capture the
various ideas here. I hope we can discuss this at the Mid-Cycle in Austin.
1) The existing
At the cinder mid-cycle it was decided that the best way to fix volumes stuck
in 'attaching' or 'detaching' was NOT to fix the broken reset-state command.
The doc string and help message for reset-state have been modified to warn the
user that the tool only affects Cinder DB and can cause
: Thursday, February 12, 2015 8:07 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] Fixing stuck volumes - part II
On Feb 11, 2015, at 3:45 PM, D'Angelo, Scott
scott.dang...@hp.commailto:scott.dang...@hp.com wrote:
At the cinder mid-cycle
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
Sent: Wednesday, February 11, 2015 5:07 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] Fixing stuck volumes - part II
On Feb 11, 2015, at 3:45 PM, D'Angelo, Scott
scott.dang
We'll have a Google Hangout for the Cinder mid-cycle for virtual attendees and
will post the links on IRC and the etherpad:
https://etherpad.openstack.org/p/cinder-liberty-midcycle-meetup
We'll make sure we ping mreidem and the Nova channel when we're discussing
Cinder - Nova topics.
We'll have a chance to discuss DB mutual exclusion at the API nodes at the
Cider mid-cyle, which starts tomorrow.
The details, issues, and realistic schedule for that will be a key piece to
this whole puzzle, since anything else is seen as a temporary solution.
-Original Message-
From:
If you create a blueprint and a spec for this, the details can be discussed in
the spec.
-Original Message-
From: Dmitry Guryanov [mailto:dgurya...@virtuozzo.com]
Sent: Tuesday, October 13, 2015 12:57 PM
To: OpenStack Development Mailing List; Maxim Nestratov
Subject: [openstack-dev]
I’m just not sure that you can evacuate with the c-vol service for those volume
down. Not without the un-safe HA active-active hacks.
In our public cloud, if the c-vol service for a backend/volumes is down, we get
woken up in the middle of the night and stay at it until we get c-vol back up.
Eduard, Gorka has done a great job of explaining some of the issues with
Active-Active Cinder-volume services in his blog:
http://gorka.eguileor.com/
TL;DR: The hacks to use the same hostname or use Pacemaker + VIP are dangerous
because of races, and are not recommended for Enterprise
Thanks Mike. You've done a great job, including making contributors feel
welcome.
-Original Message-
From: Mike Perez [mailto:thin...@gmail.com]
Sent: Monday, September 14, 2015 10:16 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [cinder] PTL Non-Candidacy
Hello
Could the work for the tooz variant be leveraged to add a truly distributed
solution (with the proper tooz distributed backend)? IF so, then +1 to this
idea. Cinder will be implementing a version of tooz based distribute locks, so
having it in Olso someday is a goal I'd think.
For those interested in various aspects of Cinder testing, we're planning on
discussing and coordinating efforts. Please join us:
#openstack-cinder
1500 UTC Wednesdays
(just before the Weekly Cinder meeting)
Testing subjects:
Multi-node Cinder testing
Active-Active HA testing
Improved Tempest
In the interest of yet-another-etherpad I created:
https://etherpad.openstack.org/p/Cinder-testing
I'll put an agenda, folks can sign up to be pinged, we'll keep the notes and
action items here, etc
From: D'Angelo, Scott
Sent: Friday, June 03, 2016 8:14
Please note that this Mailing List is not for usage questions. It is for
development issues.
You can reset the state of the volume and then delete it (admin only):
cinder reset-state #sets to available
From: Will Zhou
Sent: Wednesday, June
The Cinder team has begun a test working group[1] with the goal of improving
coverage and quality.
We meet Weekly[2] at 1500 UTC in #openstack-cinder and would welcome anyone
interested in providing expertise in Tempest/Infra/QA.
Our Cinder team contributors have a smattering of knowledge and
There is currently no simple way to clean up Cinder attachments if the Nova
node (or the instance) has gone away. We’ve put this topic on the agenda for
the Cinder mid-cycle this week:
https://etherpad.openstack.org/p/mitaka-cinder-midcycle
Cinder team is proposing to add support for API microversions [1]. It came up
at our mid-cycle that we should add a new /v3 endpoint [2]. Discussions on IRC
have raised questions about this [3]
Please weigh in on the design decision to add a new /v3 endpoint for Cinder for
clients to use when
I can do a presentation on microversions.
Scott D'Angelo (scottda)
-- Original Message --
>From : Gorka Eguileor
Subject : [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's
new complex features in Design Summit
Hi,
As you all probably know, during this cycle we
I'll throw this out there: Fort Collins HPE site is available.
Scott D'Angelo (scottda)
From: Sean McGinnis [sean.mcgin...@gmx.com]
Sent: Tuesday, April 12, 2016 8:05 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Cinder] Newton
Matt, changing Nova to store the connector info at volume attach time does
help. Where the gap will remain is after Nova evacuation or live migration,
when that info will need to be updated in Cinder. We need to change the Cinder
API to have some mechanism to allow this.
We'd also like Cinder
I like the idea of a Cinder Wishlist or perhaps titled: Cinder Future Design
and Architecture list. I think the Cinder community could benefit if we
continued to refine the work we did on this Wishlist at the Mitaka midcycle and
spent a few minutes each cycle going over the list, prioritizing,
+1 to making the testing process better.
It has been discussed that services could/should consider devoting some or all
of a release cycle to stability and/or quality.
I propose the Cinder team makes improving and fixing the tests and test process
a priority for the Newton cycle.
Scott D'Angelo
I don't think we actually should be moving all the extensions to core, just the
ones that are supported by all vendors and fully vetted. In other words, we
should be moving extensions to core based on the original intent of extensions.
That would mean that for backups we could continue to use
We've decided to meet each week to discuss status, patches, and testing of
Cinder-volume Active-Active HA:
Tuesdays 1600 UTC in openstack-cinder (same time as weekly meeting, one day
earlier)
https://etherpad.openstack.org/p/cinder-active-active-HA
If a volume is attached to an instance, and the instance is deleted, the volume
will be DETACHED, but the volume will still exist, it will NOT be DELETED.
It is up to the volume owner to delete the volume if they wish.
From: Will Zhou
Sent:
Thanks Everyone!
Scott(da)
From: Sean McGinnis
Sent: Wednesday, July 6, 2016 3:12:57 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core
I'm a little late following
FYI, Cinder implemented using the style recommended by the API-wg:
https://review.openstack.org/#/c/224910
From: Sean Dague
Sent: Monday, June 20, 2016 6:32:10 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Version header
The cinder team would welcome submission of any missing Tempest test cases. I'm
not certain of the history of the os-force_detach API, but you could write
tests for them and they would be reviewed.
Scott D'Angelo
From: joehuang
Sent:
Please keep in mind that Nova keeps some volume state in the BlockDeviceMapping
table. Without changes to Nova, a force_detach function is not complete.
I am interested in this use case, as are other Cinder developers. Please feel
free to contact me in IRC with questions as "scottda".
Scott
We added this patch to the cinderclient:
b76f5944130e29ee1bf3095c966a393c489c05e6
Which basically only shows help for the features available at the requested API
version. It is by design.
From: Sean McGinnis
Sent: Wednesday, October 12,
34 matches
Mail list logo