Vincent,
So sorry you were not feeling well during the tour. Those things happen
though...No worries.
We were glad to get the e-mail letting us know that you were ok and
feeling better!
Glad that you could join us on the trip and see the Alpine lake and get
pictures with us. I will send
Mitsuhiro,
I had already put a +2 on this, so I am agreeable to an FFE.
Mike or John, what are your thoughts?
Jay
On 04/06/2015 06:27 PM, Mitsuhiro Tanino wrote:
Hello,
I would like to get a FFE for patch https://review.openstack.org/#/c/161328/.
This patch fixes the volume migration probl
Rajini,
This is a relatively small change.
Mike, what do you think about granting an Exception for this?
Jay
On 04/06/2015 04:33 PM, rajini_...@dell.com wrote:
*Dell - Internal Use - Confidential *
Hi
Can we have a freeze exception on this CR pl?
https://review.openstack.org/154123
Clos
Anita,
My apologies. The original communication on the issue came from Mike
via the mailing list so I was attempting to continue the public
discussion here.
I will make sure to not do this in the future.
Jay
On 04/06/2015 03:19 PM, Anita Kuno wrote:
On 04/06/2015 04:03 PM, Jay S. Bryant
All,
I just wanted to provide an update on 3rd Party CI Testing for IBM's
drivers.
It was noted late last month that not all of IBM's drivers were running
the required 304 test cases. That issue has been resolved for all 3rd
Party CI's except for DS8k. The maintainer of that system has bee
+1000
You have done a great job Doug! Thank you for your leadership!
Jay
On 04/03/2015 08:11 AM, Flavio Percoco wrote:
On 03/04/15 08:50 -0400, Doug Hellmann wrote:
Team,
I have decided not to run for PTL for Oslo for the next cycle.
Serving as PTL for the last three releases has been a re
All,
Let me start with the TLDR;
Cinder, Nova and Neutron have lots of configuration options that need to
be processed by oslo-config-generator to create the
.conf.sample file. There are a couple of different ways this
could be done. I have one proposal out, which has raised concerns,
ther
Mike,
Looks like this removal may have been a mistake. We should readdress.
Jay
On 03/20/2015 05:59 AM, Erlon Cruz wrote:
I agree with John (comment on the mentioned patchset). Also, I
expected one change removing all drivers that does not report on CI.
There's one of us (HUSDriver) that is
Duncan,
If you see any of these coming out of Cinder (not oslo) please get a bug
to me.
I think I have them all removed but need to know if I have missed anything.
Thanks!
Jay
On 03/12/2015 04:24 AM, Duncan Thomas wrote:
ubuntu@devstack-multiattach:~/devstack$ cinder-manage db sync
/usr/loc
All,
I will sponsor this.
Patch just needs to be rebased.
Jay
On 03/11/2015 10:20 AM, Tom Barron wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I hereby solicit a feature freeze exception for the NFS backup review [1].
Although only about 140 lines of non-test code, this review comple
All,
Several members of the Cinder team and I were discussing the current
state of volume replication while trying to figure out the best way to
resolve bug 1383524 [1]. The outcome of the discussion was a decision
to hold off on integrating volume replication support for additional
drivers.
All,
One of the concerns raised with regards to volume migration was the lack
of tempest testing for the functionality. Since they I have had some
interest indicated in helping this effort. So, to get things started I
have created an etherpad to track development of such test cases and to
s
Mike,
A FFE for this has been submitted to Nova and is being sponsored by Matt
Riedemann: [1]
Assuming that goes through soon, can we please re-address?
Thanks!
Jay
[1]
http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg45430.html
On 02/09/2015 12:23 PM, Mike Perez wrote:
All,
In discussion with Mike Perez earlier this week the following bugs were
highlighted in Volume Migration and Volume Replication. IBM is focusing
on investigating and resolving these bugs.
I will be putting out updates as we progress towards resolution of these
issues.
Replication:
/h
All,
I have updated the mid-cycle meetup etherpad
(https://etherpad.openstack.org/p/cinder-kilo-midcycle-meetup) with more
details with regards to finding the right building on the IBM site and
have also added my cell phone number to the notes. Please don't
hesitate to call or text me with q
I think what we discussed was that existing drivers were supposed to
have something working by the end of k-2, or at least have something
close to working.
For new drivers they had to have 3rd party CI working by the end of Kilo.
Duncan, correct me if I am wrong.
Jay
On 01/10/2015 04:52 PM, M
Mike,
Thanks for putting this out there again.
A reminder, if you are planning to attend, please update the etherpad so
that I can get an accurate number in attendance and get all the security
details set up.
Thank you!
Jay
On 01/10/2015 04:00 PM, Mike Perez wrote:
The meetup will be in A
Ihar,
I agree that we should do something to enforce using the appropriate
namespace so that we don't have the wrong usage sneak in.
I haven't gotten any rules written yet. Have had to attend to a family
commitment the last few days. Hope that I can tackle the namspace
changes next week.
Minwoo,
The cherry-picks for the contain-updater and object-updater back to
stable/juno are now available for review:
https://review.openstack.org/146211 and https://review.openstack.org/134082
Jay
On 01/08/2015 09:21 AM, Minwoo Bae wrote:
Hi, to whom it may concern:
Jay Bryant and I woul
Minwoo,
It is important to understand that Icehouse has gone into a security
fixes only mode. It is too late in the stable process to be making
notable changes for anything other than security issues.
The patch for the fork bomb like problem in object-auditor is in
Icehouse: https://review
Steven,
Thank you for continuing to pursue this. Adding this functionality and
having it consistent will be a good thing.
The plan for Cinder looks good to me and is consistent with Mike and
Duncan's input.
I look forward to seeing patches for Cinder.
Jay
On 01/06/2015 10:03 AM, Steven K
All,
We have been getting a number of non-security patches proposed to
stable/icehouse for Cinder. The cores were discussing what was ok to
put into icehouse at this point in time and couldn't agree as to whether
we were at the point of only accepting security changes.
Appreciate advice on
John and Ramy,
Thanks for the feedback. So, we will create an IBM Storage CI Check
account and slowly deprecate the multiple accounts as we consolidate the
hardware.
Jay
On 12/23/2014 08:11 PM, Asselin, Ramy wrote:
I agree with John. Option 4: one ci account for all drivers.
The only val
John,
Thank you for starting this discussion and Doug, thank you for
clarifying. Your explanation below helps a lot!
Jay
On 12/22/2014 12:13 PM, Doug Hellmann wrote:
On Dec 22, 2014, at 1:05 PM, John Griffith wrote:
On Mon, Dec 22, 2014 at 10:03 AM, Ben Nemec wrote:
On 12/22/2014 09:4
Dave,
My apologies. We have not yet set a day that we are freezing BP/Spec
approval for Cinder.
We had a deadline in November for new drivers being proposed but haven't
frozen other proposals yet. I mixed things up with Nova's 12/18 cutoff.
Not sure when we will be cutting off BPs for Cin
On 12/04/2014 05:01 PM, Alan Pevec wrote:
2014-12-04 23:00 GMT+01:00 Jay S. Bryant :
Finally was able to get the master version through the gate and
cherry-picked it here:
https://review.openstack.org/#/c/139194/
That one has made it through the check. So, if it isn't too late, it coul
On 12/03/2014 01:17 PM, Alan Pevec wrote:
2014-12-02 17:15 GMT+01:00 Jay S. Bryant :
Cinder
https://review.openstack.org/137537 - small change and limited to the
VMWare driver
+1 I think this is fine to make an exception for.
one more Cinder exception proposal was added in StableJuno
On 12/02/2014 07:22 AM, Alan Pevec wrote:
Hi all,
here are exception proposal I have collected when preparing for the
2014.2.1 release,
stable-maint members please have a look!
General: cap Oslo and client library versions - sync from
openstack/requirements stable/juno, would be good to inclu
On 12/02/2014 02:31 AM, Alan Pevec wrote:
What is the text that should be included in the commit messages to make sure
that it is picked up for release notes?
I'm not sure anyone tracks commit messages to create release notes.
Let's use existing DocImpact tag, I'll add check for this in the
r
On 11/25/2014 08:10 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/11/14 20:17, Jay S. Bryant wrote:
All,
This is a question I have been struggling with for Cinder recently.
Where do we draw the line on backports. How do we handle config changes?
One thing
Monty,
I agree that upgrade is not a significant concern right now if the
existing driver is not working.
Drew,
I am having trouble following where you guys are currently at with this
work. I would like to help get you guys up and going during Kilo.
I am concerned that maybe there is conf
All,
For those of you that weren't able to make the Kilo meet-up in Paris I
wanted to send out a note regarding Cinder's Kilo mid-cycle meet-up.
IBM has offered to host it in, warm, sunny, Austin, Texas. The planned
dates are January 27, 28 and 29, 2015.
I have put together an etherpad wit
Drew,
I would say that it would be good to open a Blueprint for this and push
the code up for review. Even if you don't have CI ready yet you can
post results of a driver cert test [1] and we can start reviewing the
code while you work on finishing up the process of getting your CI running.
All,
This is a question I have been struggling with for Cinder recently.
Where do we draw the line on backports. How do we handle config changes?
One thing for Cinder I am also considering, in addition to whether it
changes the default functionality, is whether it is specific to the
submitt
On 11/14/2014 03:31 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/11/14 09:14, Flavio Percoco wrote:
On 13/11/14 23:25 +, Amrith Kumar wrote:
At the suggestion of Doug Hellmann, and relative to a
conversation with him and Flavio at Summit. Doug suggested
On 10/02/2014 11:14 AM, Jay Pipes wrote:
On 10/02/2014 11:23 AM, Jay S. Bryant wrote:
As I re-read this I think maybe you have answered my question but want
to be clear. You feel that 'State' is the only term that should be
used. Based on the definitions above, that would make
Good questions!
Jay, I have a request for some clarification in-line.
On 10/01/2014 01:37 PM, Jay Pipes wrote:
Hi Akihiro!
IMO, this is precisely where having an API standards working group can
help to make the user experience of our public APIs less frustrating.
Such a working group should
On 09/26/2014 06:46 PM, Matt Riedemann wrote:
On 9/25/2014 11:04 AM, Ben Nemec wrote:
+1. He's on the short list of people who actually understand how all
that lazy translation stuff works. :-)
-Ben
On 09/23/2014 04:03 PM, Doug Hellmann wrote:
James Carey (jecarey) from IBM has done the 3r
John,
Thank you for being welcoming to me when I started with Cinder during
Havana and for all the mentoring and encouragement you have given since
then.
I think the fact that Cinder is such a great group to work with has a
lot to owe to your leadership and guidance. Thank you!
I look for
On 09/21/2014 07:37 PM, Matt Riedemann wrote:
On 9/19/2014 8:13 AM, Sean Dague wrote:
I've spent the better part of the last 2 weeks in the Nova bug tracker
to try to turn it into something that doesn't cause people to run away
screaming. I don't remember exactly where we started at open bug
Alon,
Thanks, I have added your request to the etherpad
https://etherpad.openstack.org/p/juno-cinder-approved-ffes and it will
undergo review.
Thanks,
Jay
On Mon, 2014-09-08 at 21:55 +0300, Alon Marx wrote:
> Hi,
>
> Please consider the following code changes as Feature Freeze
> Exceptions.
Great nomination Walt. Thank you!
+1
Thank you Xing for your contributions!
Jay
On Thu, 2014-08-14 at 06:55 +, Boring, Walter wrote:
> Hey guys,
>I wanted to pose a nomination for Cinder core.
>
> Xing Yang.
> She has been active in the cinder community for many releases and has worke
John,
I spent the drive to the Minneapolis Airport thinking about this chain
of e-mails. Hope these thoughts help ...
On Thu, 2014-08-07 at 07:55 -0600, John Griffith wrote:
>
>
>
>
> On Thu, Aug 7, 2014 at 7:33 AM, Anne Gentle
> wrote:
>
>
>
> On Thu, Aug
Josh,
I agree that the mailing list is a hard place to provide such guidance
and direction. I find mailing lists intimidating. Had taken me some
time to be comfortable submitting here.
After my response to this note the other day I was pinged internally via
our messaging client asking for some
Johnson,
I am not sure what you mean by 'attach volume manually'. Do you mean
when you do a 'nova volume-attach'? If so, then, yes, the process will
use the appropriate iscsi_helper and iscsi_ip_address to configure the
attachment.
Does that answer your question?
Jay
On Mon, 2014-07-21 at 12:
Abbass,
There has been discussion around this in the past.
As it would be a significant feature you should open a spec for it. Do
a 'git clone https://github.com/openstack/cinder-specs.
There are directions in there for actually submitting the spec.
Thanks!
Jay
On Fri, 2014-07-18 at 09:01 +02
Mike,
Thanks for pointing this out. I thought I had gotten all of these and
this supports the need for the hacking check I will work on.
We also hit errors like this on our internal CI due to a bad merge.
Anyway, I am on top of this. Will fix asap.
Jay
On Sun, 2014-07-20 at 15:49 -0700, Mike
Thanks Duncan and also Dolph, I should have made the question
broader. :-)
On Wed, 2014-07-16 at 13:22 +0100, Duncan Thomas wrote:
> On 16 July 2014 03:57, Jay S. Bryant wrote:
> > John,
> >
> > So you have said a few times that the specs are a learning process.
> >
I agree that there are cases where a bug is overkill and it would be
nice to add a note showing I did put some thought into doing the recheck
no bug. Just my two cents.
On Wed, 2014-07-16 at 17:07 +0100, Derek Higgins wrote:
> On 16/07/14 14:48, Steve Martinelli wrote:
> > What are the benefits o
John,
So you have said a few times that the specs are a learning process.
What do you feel with have learned thus far using specs? I think you
had the hope that it would help organize targeting blueprints and not
missing things for a release. Do you feel that is working?
I would like to hear mo
Boden,
Thanks for bringing this up:
On Thu, 2014-06-26 at 12:14 -0400, boden wrote:
> We were recently having a discussion over here in trove regarding a
> standardized format to use for log and error messages - obviously
> consistency is ideal (within and across projects). As this discussion
Mardan,
Note, you will also need to follow the new Cinder Specs process for Juno
BluePrints. You can find details here: [1]
Jay
[1]
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-05-28-16.00.log.html#l-437
On Wed, 2014-05-07 at 18:48 +0530, Swapnil Kulkarni wrote:
> Missed som
not need, then great, makes review and merge even easier.
>
> Thanks
>
> On 28 April 2014 17:03, Jay S. Bryant wrote:
> > Duncan,
> >
> > Thanks for the response. Have some additional thoughts, in-line, below:
> >
> >
> > On Mon, 2014-04-28 at 1
On Wed, 2014-04-30 at 10:20 -0700, Mike Perez wrote:
> On 06:49 Wed 30 Apr , Zhangleiqiang (Trump) wrote:
> > Hi stackers:
> >
> > I found when a instance status become "error", I will see the detailed
> > fault info at times when I "show" the detail of Instance. And it is very
> > conv
about it, I don't know that the debug translation removal
needs to be dependent, but we could work it out that way if you feel
that is important.
Let me know what you think.
Thanks!
> On 27 April 2014 00:20, Jay S. Bryant wrote:
> > All,
> >
> > I am looking for feedba
All,
I am looking for feedback on how to complete implementation of i18n
support for Cinder. I need to open a new BluePrint for Juno as soon as
the cinder-specs process is available. In the mean time I would like to
start working on this and need feedback on the scope I should undertake
with thi
On Thu, 2014-04-24 at 15:11 -0700, Walter A. Boring IV wrote:
> On 04/23/2014 05:09 PM, Jay S. Bryant wrote:
> > All,
> >
> > I have gotten questions from our driver developers asking for details
> > regarding the move to using cinder-specs for proposing Blueprints. I
&
All,
I have gotten questions from our driver developers asking for details
regarding the move to using cinder-specs for proposing Blueprints. I
brought this topic up in today's Cinder Weekly Meeting, but the meeting
was lightly attended so we decided to move the discussion here.
I am going to pu
in?
Appreciate your thoughts on the subject!
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Ma
From: Brant Knudson
To: "OpenStack Development Mailing List (not for usage questions)"
,
Date: 03/14/2014 02:21 PM
Subject:Re: [openstack-dev] [Oslo] Improving oslo-incubator
update.py
On Fri, Mar 14, 2014 at 2:05 PM, Jay S Bryant wrote:
It would be great i
From: Duncan Thomas
To: "OpenStack Development Mailing List (not for usage questions)"
,
Date: 03/14/2014 11:56 AM
Subject:Re: [openstack-dev] Duplicate code for processing REST
APIs
On 13 March 2014 21:13, Roman Podoliaka wrote:
> Hi Steven,
>
> Code from openstack/common/
From: Duncan Thomas
To: "OpenStack Development Mailing List (not for usage questions)"
,
Date: 03/14/2014 11:49 AM
Subject:Re: [openstack-dev] [Oslo] Improving oslo-incubator
update.py
On 14 March 2014 16:10, Jay S Bryant wrote:
> --> Duncan, It is import
From: Brant Knudson
To: "OpenStack Development Mailing List (not for usage questions)"
,
Date: 03/14/2014 10:26 AM
Subject:Re: [openstack-dev] [Oslo] Improving oslo-incubator
update.py
On Wed, Mar 12, 2014 at 11:03 AM, Duncan Thomas
wrote:
On 15 January 2014 18:53, Brant
penstack.org/cgi-bin/mailman/listinfo/openstack-dev
All,
Thanks for taking the time to consider/discuss this.
Some good lessons learned on this end.
Look forward to getting this in early in Juno.
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member___
we are talking about *another* oslo sync.
-1
-Sean
--
Sean Dague
Samsung Research America
s...@dague.net / sean.da...@samsung.com
http://dague.net
[attachment "signature.asc" deleted by Jay S Bryant/Rochester/IBM]
___
OpenStac
From: Brian Cline
To: openstack-dev@lists.openstack.org,
Date: 03/04/2014 12:29 PM
Subject:Re: [openstack-dev] Proposal to move from Freenode to OFTC
On 03/04/2014 05:01 AM, Thierry Carrez wrote:
> James E. Blair wrote:
>> Freenode has been having a rough time lately due to a s
I would agree. I don't think that Cinder should/could be able to act upon
Nova's state for the VM. Force-delete is really in place as a backup to
clean-up after certain failures in Cinder. Other mechanisms are in place
to handle issues in Nova.
Jay S. Bryant
IBM Cind
Response marked with >> below.
Jay
From: Doug Hellmann
To: "OpenStack Development Mailing List (not for usage questions)"
,
Date: 02/19/2014 09:22 AM
Subject:Re: [openstack-dev] [oslo] Some questions about Rest API
and log messages translation
On Tue, Feb 18, 2014 at 1
ning again.
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail: jsbry
Joe,
Ah! So, those aren't for Cinder Volume but for nova-volume. Ok, so there
isn't really a bug then.
Sorry for speaking too quickly. Thanks for the info!
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E
Pat,
I see the same behavior on an Icehouse level install. So, I think you may
have found a bug.
I would open the bug to python-novaclient to start with, but it may end up
coming back to Cinder.
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department
Mike,
Great idea!
I can participate remotely.
Let me know how I can be of the best help!
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-42
Sean and John,
I would be happy to help out with this for Cinder.
Let me know how I can help.
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line:
There is already an option that can be set in cinder.conf using
'volume_clear=none'
Is there a reason that that option is not sufficient?
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
T
John,
I am flexible.
I am fine with trying to move the time to 04:00 or 05:00 UTC or we can
alternate. The one concern with alternation is that it may lead to
confusion and less attendance, but I am certainly open to trying it.
Jay S. Bryant
IBM Cinder Subject Matter Expert
good commit
message structure. When combined with FlySpell many of the simple
mistakes can be avoided.
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX
Agreed that any -1's should require a suggestion for a way to resolve the
issue. I haven't seen people -1'ing without suggestions for improvement
though. I think, generally, people help explain why a change is needed.
Jay S. Bryant
Linux Developer -
OpenStack Ent
ided.
The point of OpenStack is to have a collaborative community. Some people
bring better spelling and grammar to the table than others as a
contribution.
Jay S. Bryant
Linux Developer -
OpenStack Enterprise Edition
Department 7YLA, Building 015-2, Office E125, Roc
available as a
result through websites like Stackalytics (http://stackalytics.com/) .
Highlighting the sponsors of individual commits seems unnecessary.
That's my two cents.
Jay S. Bryant
Linux Developer -
OpenStack Enterprise Edition
Department 7YLA, Building 015
201 - 279 of 279 matches
Mail list logo
