Oops. sorry. I was as stack user. It works now (with a sudo). All the three
cinder services are running.
Thanks a ton for the help,
Pradip
On Tue, Jan 5, 2016 at 5:51 PM, Pradip Mukhopadhyay <
pradip.inte...@gmail.com> wrote:
> Thanks. Tried this. Still getting the same error on c-api inst
War and Peace
or
Notes from the Cinder Mitaka Midcycle Sprint
January 26-29
Etherpads from discussions:
* https://etherpad.openstack.org/p/mitaka-cinder-midcycle-day-1
* https://etherpad.openstack.org/p/mitaka-cinder-midcycle-day-2
* https://etherpad.openstack.org/p/mitaka-cinder-midcycle-day-3
*
On 08/17/2015 11:53 AM, Mike Perez wrote:
Getting rid of API extensions
=
Move obvious things over (volume attach, type manager) to core API controllers.
Deprecate existing extensions and have these use core API controller code. Get
rid of the silly os- prefix in endpo
On Mon, Aug 17, 2015 at 08:53:29AM -0700, Mike Perez wrote:
> A *summary* of the Cinder midcycle sprint, in attempt to keep your attention.
> Full meeting notes available [1].
>
> [ ... ]
>
> -- Mike Perez
Thank you very much for the summary.
Cheers,
Gorka.
Great summary. We covered a lot of ground.
Thanks Mike!
On 08/17/2015 10:53 AM, Mike Perez wrote:
A *summary* of the Cinder midcycle sprint, in attempt to keep your attention.
Full meeting notes available [1].
Image Caching
=
Glance Cinder backend store + Cinder Image Caching are
On Thu, Aug 20, 2015 at 8:27 PM, yang, xing wrote:
> Hi Mike,
>
> I’m wondering if you can consider approving the following blueprints. They
> were submitted late:(. These are good to be used as reference
> implementations for the new features, so I think it is good to have them.
>
> https://blu
Thanks Mike for summary. About the Getting rid of API extensions, I'd
like help to move the extensions over to the core. Do we should begin this
work at Mitaka?
2015-08-17 23:53 GMT+08:00 Mike Perez :
> A *summary* of the Cinder midcycle sprint, in attempt to keep your
> attention.
> Full meeti
The Microsoft CI has been disabled since July 22nd [1].
Last I heard from the Cinder midcycle sprint, this CI was still not
ready and it hasn't been for 30 days now.
Where are we with things, and why has communication been so poor with
the Cloud Base solutions team?
[1] -
http://lists.openstack
Hi,
Why the permission of cinder.conf is set to 640 not 600? Can we set it to 600
instead of 640 and is there any problems if we change it?
Any input will be appreciate, thanks!
Wilson Liu
__
OpenStack Development Mailing L
Hi,
I would like to request feature freeze exception for the implementation of
capacity-headroom.
It calculates virtual free memory and send notifications to the ceilometer
together with other storage capacity stats.
Blueprint:
https://blueprints.launchpad.net/cinder/+spec/capacity-headroom
Spe
On 09/14/2015 12:15 PM, Mike Perez wrote:
Hello all,
I will not be running for Cinder PTL this next cycle. Each cycle I ran
was for a reason [1][2], and the Cinder team should feel proud of our
accomplishments:
* Spearheading the Oslo work to allow *all* OpenStack projects to have
their databas
> -Original Message-
> From: Mike Perez [mailto:thin...@gmail.com]
> Sent: Monday, September 14, 2015 6:16 PM
>
> Hello all,
>
> I will not be running for Cinder PTL this next cycle. Each cycle I ran was
> for a
> reason [1][2], and the Cinder team should feel proud of our
> accomplishme
Thanks Mike. Enjoy a break (albeit thin and brief.) I've appreciated your
guiding the Cinder cats.
On Mon, Sep 14, 2015 at 10:15 AM, Mike Perez wrote:
> Hello all,
>
> I will not be running for Cinder PTL this next cycle. Each cycle I ran
> was for a reason [1][2], and the Cinder team should fee
On Mon, Sep 14, 2015 at 09:15:44AM -0700, Mike Perez wrote:
> Hello all,
>
> I will not be running for Cinder PTL this next cycle. Each cycle I ran
> was for a reason [1][2], and the Cinder team should feel proud of our
> accomplishments:
Thanks for a couple of awesome cycles Mike!
_
On 9/14/15 12:15 PM, Mike Perez wrote:
> Hello all,
>
> I will not be running for Cinder PTL this next cycle.
Thanks for helping make me feel welcome as I started up,
for your example of gutsy and consistent leadership,
and for some really good coffee!
-- Tom
Thanks for your leadership and service Mike. You've done a great job!
Walt
Hello all,
I will not be running for Cinder PTL this next cycle. Each cycle I ran
was for a reason [1][2], and the Cinder team should feel proud of our
accomplishments:
* Spearheading the Oslo work to allow *all* Open
Mike, you've been an awesome help for me getting started in Cinder. Thanks
for all your hard work as PTL!
-Patrick
On Mon, Sep 14, 2015 at 10:19 AM, Walter A. Boring IV
wrote:
> Thanks for your leadership and service Mike. You've done a great job!
>
> Walt
>
>> Hello all,
>>
>> I will not be
Mike,
Thank you for doing this hard work!
Regards,
Ivan Kolodyazhny
On Mon, Sep 14, 2015 at 8:27 PM, Patrick East
wrote:
> Mike, you've been an awesome help for me getting started in Cinder. Thanks
> for all your hard work as PTL!
>
> -Patrick
>
> On Mon, Sep 14, 2015 at 10:19 AM, Walter A. B
Mailing List
Subject: [openstack-dev] [cinder] PTL Non-Candidacy
Hello all,
I will not be running for Cinder PTL this next cycle. Each cycle I ran was for
a reason [1][2], and the Cinder team should feel proud of our
accomplishments:
* Spearheading the Oslo work to allow *all* OpenStack projects
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
On Mon, Sep 14, 2015 at 11:02 AM, Sean McGinnis
wrote:
> On Mon, Sep 14, 2015 at 09:15:44AM -0700, Mike Perez wrote:
> > Hello all,
> >
> > I will not be running for Cinder PTL this next cycle. Each cycle I ran
> > was for a reason [1][2], and the Cinder team should feel proud of our
> > accompli
Thanks Mike ! Your help is very important to me to get started in
cinder and we do a lot of proud work with your leadership.
2015-09-15 6:36 GMT+08:00 John Griffith :
>
>
> On Mon, Sep 14, 2015 at 11:02 AM, Sean McGinnis
> wrote:
>>
>> On Mon, Sep 14, 2015 at 09:15:44AM -0700, Mike Perez wrote:
>
Thanks Mike. Thank you for doing a great job.
> From: sxmatch1...@gmail.com
> Date: Tue, 15 Sep 2015 10:05:22 +0800
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [cinder] PTL Non-Candidacy
>
> Thanks Mike ! Your help is very important to me to get start
Thanks Mike!
That was really demanding work!
2015-09-15 9:27 GMT+02:00 陈莹 :
> Thanks Mike. Thank you for doing a great job.
>
>
> > From: sxmatch1...@gmail.com
> > Date: Tue, 15 Sep 2015 10:05:22 +0800
> > To: openstack-dev@lists.openstack.org
> > Subject: Re:
for doing a great job.
>>
>>
>> > From: sxmatch1...@gmail.com
>> > Date: Tue, 15 Sep 2015 10:05:22 +0800
>> > To: openstack-dev@lists.openstack.org
>> > Subject: Re: [openstack-dev] [cinder] PTL Non-Candidacy
>>
>> >
>> > Thanks Mi
Mike,
We were enabled to do some great things under your leadership. Cinder
has greatly benefited from your time as a PTL.
Thanks for all you have done!
Jay
On 09/14/2015 11:15 AM, Mike Perez wrote:
Hello all,
I will not be running for Cinder PTL this next cycle. Each cycle I ran
was for a
Hi John,
Thank you for these question. Such questions with answers could be a good
part of PTL proposal in the future.
Please, see my answers inline.
Regards,
Ivan Kolodyazhny
On Sun, Sep 20, 2015 at 8:30 PM, John Griffith
wrote:
> PTL nomination emails are good, but I have a few questions t
On Sun, Sep 20, 2015 at 11:30:15AM -0600, John Griffith wrote:
> PTL nomination emails are good, but I have a few questions that I'd like
> to ask to help me in making my vote. Some of these are covered in the
> general proposal announcements, but I'd love to hear some more detail.
>
> It would
Hi John. Thanks for the questions.
> 1. Do you actually have the time to spend to be PTL
>
I'm very much aware, and discussed with my management prior to standing,
that being PTL is a pretty much full time job. I realise I'm somewhat
limited by not being in a US time zone, however I'm pretty fle
John,
Thanks for the questions, it Ill really help me to make a the best choice.
I hadn't pondered the first question . +1 to make those and other if
suggest part of the candidate proposal.
Erlon
On Mon, Sep 21, 2015 at 6:49 AM, Duncan Thomas
wrote:
> Hi John. Thanks for the questions.
>
>
>>
>
> 1. Do you actually have the time to spend to be PTL
>
> I don't think many people realize the time commitment. Between being
> on top of reviews and having a pretty consistent view of what's going
> on and in process; to meetings, questions on IRC, program management
> type stuff etc. Do you f
Hello everyone,
Cinder and Designate just produced their first release candidate for the
end of the Liberty cycle. The RC1 tarballs, as well as a list of
last-minute features and fixed bugs since liberty-1 are available at:
https://launchpad.net/cinder/liberty/liberty-rc1
https://launchpad.net/de
This message is for all new vendors looking to add a new Cinder driver
in the Mitaka release as well as any existing vendors that need to add a
new protocol/driver to what is already in tree.
There has been some discussion on the mailing list and in the IRC
channel about changes to our policy arou
On Thu, Mar 17, 2016 at 09:41:31AM +0100, Thierry Carrez wrote:
> Hello everyone,
>
> Cinder is the next project team to produce a release candidate for
> the end of the Mitaka cycle! You can find the RC1 source code
> tarball at:
>
> https://tarballs.openstack.org/cinder/cinder-8.0.0.0rc1.tar.gz
Hello Team,
It's a big honor for me be a part of the our Cinder community and I do my
best
to make Cinder better. That's why I'm I'm announcing my candidacy for
Cinder PTL for the Mitaka release. That doesn't mean that I'm working at
half
strength now. It means that I would like to give as much be
3:03 PM
To: OpenStack Development Mailing List ;
openst...@lists.openstack.org
Subject: [openstack-dev] [Cinder] Mitaka RC2 available
Due to release-critical issues spotted in Cinder during RC1 testing, a new
release candidate was created for Mitaka. You can find the RC2 source code
tarballs at
:thie...@openstack.org]
> Sent: 29 March 2016 3:03 PM
> To: OpenStack Development Mailing List ;
> openst...@lists.openstack.org
> Subject: [openstack-dev] [Cinder] Mitaka RC2 available
>
> Due to release-critical issues spotted in Cinder during RC1 testing, a new
> releas
Great, thanks!
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: 29 March 2016 4:01 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: openst...@lists.openstack.org
Subject: Re: [openstack-dev] [Cinder] Mitaka RC2 available
That patch is now approved and in the
Hi Chen,
Not sure if I got you right but I brought this topic in #openstack-cinder
some days ago. The idea is to be able to rollback a snapshot in Cinder.
Today what is possible to do is to create a volume from a snapshot. From
the user point of view, this is not ideal, as there are several cases,
user's scenarios and determin what to do next step.
>
>
>
> Sincerely,
>
> zongliang chen
>
>
>
> *发件人:* Erlon Cruz [mailto:sombra...@gmail.com]
> *发送时间:* 2016年4月5日 2:50
> *收件人:* OpenStack Development Mailing List (not for usage questions)
> *抄送:*
time to gather
>>
>> the user's scenarios and determin what to do next step.
>>
>>
>>
>> Sincerely,
>>
>> zongliang chen
>>
>>
>>
>> *发件人:* Erlon Cruz [mailto:sombra...@gmail.com]
>> *发送时间:* 2016年4月5日 2:50
>>
and determin what to do next step.
>>>
>>>
>>>
>>> Sincerely,
>>>
>>> zongliang chen
>>>
>>>
>>>
>>> *发件人:* Erlon Cruz [mailto:sombra...@gmail.com]
>>> *发送时间:* 2016年4月5日 2:50
>>> *收件人:* OpenStack
o the following links. May be more user scenario we should
>>>> considered,such as backup,create volume from snapshot,consistency group and
>>>> etc,we will spend some time to gather
>>>>
>>>> the user's scenarios and determin what to
gt;>>> according to the following links. May be more user scenario we should
>>>>> considered,such as backup,create volume from snapshot,consistency group
>>>>> and
>>>>> etc,we will spend some time to gather
>>>>>
>>>
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] [Cind
ubject: Re: [openstack-dev] [Cinder] Newton Midcycle Planning
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
On 04/12/2016 10:05 AM, Sean McGinnis wrote:
> Hey Cinder team (and those interested),
>
> We've had a few informal conversations on the channel and in meetings,
> but wanted to capture some things here and spread awareness.
>
> I think it would be good to start planning for our Newton midcycle.
HP facility just outside Dublin (ireland) is available again, depending on
dates
On 12 April 2016 at 17:05, Sean McGinnis wrote:
> Hey Cinder team (and those interested),
>
> We've had a few informal conversations on the channel and in meetings,
> but wanted to capture some things here and sprea
>> Regards,
>>>>> Ivan Kolodyazhny,
>>>>> http://blog.e0ne.info/
>>>>>
>>>>> On Thu, Apr 7, 2016 at 12:00 PM, Chenzongliang <
>>>>> chenzongli...@huawei.com> wrote:
>>>>>
>>>>
Sean,
Thanks for getting the discussion started.
I think R-14 might be a little tricky leading up to the 4th of July weekend.
It seems like R-17 is coming awful quick but could be done. That or
R-11 would be my second vote then.
We have had successful meet-ups in Rochester ... yes, the gues
On 04/12/2016 07:21 PM, Jay S. Bryant wrote:
> Sean,
>
> Thanks for getting the discussion started.
>
> I think R-14 might be a little tricky leading up to the 4th of July
> weekend.
>
> It seems like R-17 is coming awful quick but could be done. That or
> R-11 would be my second vote then.
R-
On Tue, Apr 12, 2016 at 09:05:18AM -0500, Sean McGinnis wrote:
All folks interested in attending the Cinder Newton Midcycle - please
fill out this survey so we can collect data to help finalize a date and
location:
https://www.surveymonkey.com/r/L2CY3RL
Thanks!
Sean
> Hey Cinder team (and thos
k.org/pipermail/openstack-dev/2015-October/077209.html
[4] https://review.openstack.org/#/c/306930/
-Original Message-
From: Michał Dulko [mailto:michal.du...@intel.com]
Sent: Thursday, April 14, 2016 7:06 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [opensta
atter. Do we have other OpenStack project
suffering from similar issue?
>
> -Original Message-
> From: Michał Dulko [mailto:michal.du...@intel.com]
> Sent: Thursday, April 14, 2016 7:06 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subj
On 19 April 2016 at 23:42, Michał Dulko wrote:
> On 04/18/2016 09:17 AM, Ramakrishna, Deepti wrote:
> > Hi Michal,
> >
> > This seemed like a good idea when I first read it. What more, the server
> code for extension listing [1] does not do any authorization, so it can be
> used for any logged in
The results are in!
We took a look at the SurveyMonkey results today, and we have now
formally set the dates and locations for the Cinder Newtone midcycle.
All are welcome and encouraged to attend!
https://etherpad.openstack.org/p/newton-cinder-midcycle
Sean (smcginnis)
On Tue, Apr 12, 2016 at
On Thu, Apr 28, 2016 at 01:30:40PM -0500, Sean McGinnis wrote:
> The results are in!
>
> We took a look at the SurveyMonkey results today, and we have now
> formally set the dates and locations for the Cinder Newtone midcycle.
>
> All are welcome and encouraged to attend!
>
> https://etherpad.op
At the Design Summit in Austin, the Cinder team met over three days
to go over a variety of topics. This is a general summary of the
notes captured from each session.
We were also able to record most sessions. Please see the
openstack-cinder YouTube channel for all its minute and tedious
glory:
h
Hi,
We now have a working CI on below patches:
https://review.openstack.org/#/c/187707/
https://review.openstack.org/#/c/187853/
@jgriffith: we will sure start to give back to community.Thanks for
pointing this out.
Regards
Nikesh
On Thu, Jun 4, 2015 at 1:46 PM, Alex Meade wrote:
> Agreed, I'd
Hey Everyone,
So I've talked a little in bits and pieces regarding the implementations
that are going in for the ABC metaclass work. First off, I think the use
of ABC is a good idea and has value, particularly as we approach/surpass 50
third party drivers.
The only thing that I'm wondering if we
Hello!
I just found the following commit in the cinder log:
commit a3f4eed52efce50c2eb1176725bc578272949d7b
Merge: 6939b4a e896ae2
Author: Jenkins
Date: Thu Jul 2 23:14:39 2015 +
Merge "Revert First version of Cinder driver for Quobyte"
Is this part of some restructuring work, etc. t
Hi all,
As you may know, we've got experimental job [1] to run functional tests [2]
for python-cinderclient with devstack setup.
Functional tests for python-cinderclient is very important because it's
almost the only way to test python-cinderclient with Cinder API. For now,
we've got only Rally w
Hello,
I'd like to (mis-)use Cinder outside of OpenStack, i.e. without Nova.
I can easily create/manage volumes themselves, Cinder API is pretty
friendly here. Now, how can I attach a volume somewhere? Something like
'nova volume-attach ', but without Nova and with
(=anything) instead of (=vir
n for replication
Thanks,
-Ruijing
From: Ronen Kat [mailto:ronen...@il.ibm.com]
Sent: Tuesday, February 3, 2015 9:41 PM
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [cinder] documenting volume replication
As some of you are aware the spec for replicati
help you add your other comments to the replication etherpad.
Thanks,
Xing
From: Guo, Ruijing [mailto:ruijing@intel.com]
Sent: Saturday, February 14, 2015 8:37 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] documenting volume replic
age side replication, do you refer to host side replication?
Ronen
From:
"Guo, Ruijing"
To:
"OpenStack Development
Mailing List (not for usage questions)"
Date:
15/02/2015 03:41 AM
Subject:
Re: [openstack-dev]
[cinder] documenting volume replicat
M
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] documenting volume replication
Hi Ruijing,
Thanks for the comments.
Re (1) - driver can implement replication in any means the driver see fit. It
can be exported and be available to the sched
Proposals for the fishbowl, working and sprint sessions with the block
storage project Cinder can be submitted now:
https://etherpad.openstack.org/p/cinder-liberty-proposed-sessions
On April 27th, we will be discussing these together in the Cinder IRC
meeting [1]. This will allow time to set thin
Hi all,
I was working on spec[1] and prototype[2] to make Cinder to be able to resume
workflows in case of server or service failure. Problem of requests lost and
resources left in unresolved states in case of failure was signaled at the
Paris Summit[3].
What I was able to prototype was to res
Hi All,
Quick update.
We added GlusterFS CI job (gate-tempest-dsvm-full-glusterfs) to *check
pipeline (non-voting)* after the patch @ [1] was merged.
Its been running successfully ( so far so good ) on Cinder patches, few
examples are in [2]
I also updated the 3rd party CI status page [3]
All vendors working on cinder third party ci are encouraged to attend the 3rd
party ci meetings.
https://wiki.openstack.org/wiki/Meetings/ThirdParty
This is a great place to ask questions, report issues, and share solutions.
Ramy
_
Hi,
I saw openstack cinder already supported iscsi & FC and didn’t support FCoE.
Any plan to support it?
Is there any BP to cover it? If not, I may draft for it.
Thanks,
-Ruijing
__
OpenStack Development Mailing List (not f
Hi,
I tested Swift backup driver in Cinder-backup and that performance isn't
high.
In our test environment, The average time for backup 50G volume is 20min.
I found a patch for this that add multi thread for swift backup driver(
https://review.openstack.org/#/c/111314) but It's also too slow. It
Hello everyone,
Next to each the release candidate stage, we have Cinder and Sahara.
Their RC1 tarballs, as well as a lists of last-minute features and fixed
bugs since kilo-3 are available at:
https://launchpad.net/cinder/kilo/kilo-rc1
https://launchpad.net/sahara/kilo/kilo-rc1
Unless release-c
On Thu, May 7, 2015 at 9:01 AM, Mike Perez wrote:
> Survey: https://www.surveymonkey.com/s/6QRKV6Z
>
> This will determine, when, where and get a rough count.
>
> We will review the results in the next Cinder Meeting [1], which is
> 2015-05-16 at 16:00 UTC on #openstack-meeting
>
> [1] - https://w
On 06/03/2015 01:32 PM, Mike Perez wrote:
> There are a couple of cases [1][2] I'm seeing where new Cinder volume
> drivers for Liberty are rebranding other volume drivers. This involves
> inheriting off another volume driver's class(es) and providing some
> config options to set the backend name,
On Wed, Jun 3, 2015 at 11:32 AM, Mike Perez wrote:
> There are a couple of cases [1][2] I'm seeing where new Cinder volume
> drivers for Liberty are rebranding other volume drivers. This involves
> inheriting off another volume driver's class(es) and providing some
> config options to set the bac
I think having the rebranded drivers is fine (yay for effective code
re-use, right?), but they shouldn't have any special treatment. I don't
like the idea of having different categories of volume drivers where some
require CI and some don't.
As far as I know, in this specific case, they already ha
On 06/03/2015 01:59 PM, John Griffith wrote:
> On Wed, Jun 3, 2015 at 11:32 AM, Mike Perez wrote:
>
>> There are a couple of cases [1][2] I'm seeing where new Cinder volume
>> drivers for Liberty are rebranding other volume drivers. This involves
>> inheriting off another volume driver's class(es
> -Original Message-
> From: Eric Harney [mailto:ehar...@redhat.com]
> Sent: Wednesday, June 03, 2015 12:54 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [cinder] Rebranded Volume Drivers
>
> On 06/03/2015 01
On 6/3/15 6:16 PM, Bruns, Curt E wrote:
>
>
>> -Original Message-
>> From: Eric Harney [mailto:ehar...@redhat.com]
>> Sent: Wednesday, June 03, 2015 12:54 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [open
On 06/03/2015 02:53 PM, Eric Harney wrote:
On 06/03/2015 01:59 PM, John Griffith wrote:
On Wed, Jun 3, 2015 at 11:32 AM, Mike Perez wrote:
There are a couple of cases [1][2] I'm seeing where new Cinder volume
drivers for Liberty are rebranding other volume drivers. This involves
inheriting
Sounds like the community would like CI's regardless, and I agree.
Just because the driver code works for one backend solution, doesn't
mean it's going to work with some other.
Lets continue with code reviews with these patches only if they have a
CI reporting, unless someone has a compelling rea
Agreed, I'd also like to mention that rebranded arrays may differ slightly
in functionality as well so the CIs would need to run against a physical
rebranded device. These differences also justify the need for letting
rebranded drivers in.
-Alex
On Thu, Jun 4, 2015 at 4:41 PM, Mike Perez wrote:
Pylint on my patch is failing with the following error:
Module 'hashlib' has no 'sha256'
Cinder pylint already has following exceptions,
pylint_exceptions:["Instance of 'sha1' has no 'update' member", ""]
pylint_exceptions:["Module 'hashlib' has no 'sha224' member", ""]
So I think "hashlib h
Hey Everyone,
I was trying to just use Launchpad to track these but there's been requests
for an etherpad similar to what Mikal put together. So here it is [1]
Thanks,
John
[1]: https://etherpad.openstack.org/p/juno-cinder-approved-ffes
___
OpenStack-
I'd like to announce my candidacy for the Block Storage (Cinder) PTL
position.
I've been involved with OpenStack for about two and a half years now,
starting out by trying to help with some things in Nova-Volumes and then
with the help of a lot of great folks creating Cinder. I have been the
unof
On Mon, Jan 20, 2014 at 10:07 AM, iKhan wrote:
> Hi,
>
> I have imported iniparse to my cinder code, it works fine when I perform
> execution. But when I run the unit test, it fails while importing iniparse.
> It says "No module named iniparse". Do I have to take care of something
> here?
>
> --
>
Thanks John,
It worked earlier while executing because iniparse was installed, tho this
wasn't present in virtual environment. Installing iniparse via pip did
work. Since I didn't install iniparse specifically, I was under impression
it was there by default. Probably now I have to take care of thi
On Mon, Jan 20, 2014 at 10:30 AM, iKhan wrote:
> Thanks John,
>
> It worked earlier while executing because iniparse was installed, tho this
> wasn't present in virtual environment. Installing iniparse via pip did work.
> Since I didn't install iniparse specifically, I was under impression it was
On Mon, Jan 20, 2014 at 11:15 AM, John Griffith
wrote:
> On Mon, Jan 20, 2014 at 10:30 AM, iKhan wrote:
>> Thanks John,
>>
>> It worked earlier while executing because iniparse was installed, tho this
>> wasn't present in virtual environment. Installing iniparse via pip did work.
>> Since I didn'
Continued with ConfigParser, nothing much difference apart from clean way
of maintaining INI file in iniparse. I think unless a solution is thought,
good to go with this.
Thanks again John.
On Mon, Jan 20, 2014 at 11:47 PM, John Griffith wrote:
> On Mon, Jan 20, 2014 at 11:15 AM, John Griffith
I am worried which one is better in terms of performance? iniparse or
ConfigParser?
I am aware iniparse will do a better job of maintaining INI file's
structure, but I am more interested in performance.
Can anyone shed some light about parser that can be used to perform INI
parsing?
On Tue, Jan
On Tue, 2014-01-21 at 08:29 +0530, iKhan wrote:
> I am worried which one is better in terms of performance? iniparse or
> ConfigParser?
>
> I am aware iniparse will do a better job of maintaining INI file's
> structure, but I am more interested in performance.
The parsing of INI files is the last
On Tue, Jan 21, 2014 at 4:06 PM, Jay Pipes wrote:
> On Tue, 2014-01-21 at 08:29 +0530, iKhan wrote:
>> I am worried which one is better in terms of performance? iniparse or
>> ConfigParser?
>>
>> I am aware iniparse will do a better job of maintaining INI file's
>> structure, but I am more interes
Folks,
I would love to get people together who are interested in Cinder stability
to really dedicate a few days. This is not for additional features, but
rather
finishing what we already have and really getting those in a good shape
before the end of the release.
When: Feb 24-26
Where: San Franci
Hello,
We want to be able to launch a VM with a number of cinder volumes on the
same host (the host is a compute and a storage node).
We're looking for a way to tell nova-scheduler to work with
cinder-scheduler so that we can filter and weight hosts according to our
needs.
According to the docume
Hello!
I have made the same work in Glance — updating glance/openstack from Oslo.
I'd appreciate your reviews and comments very much.
https://review.openstack.org/#/c/46088/
https://review.openstack.org/#/c/46955/
https://review.openstack.org/#/c/48195/
Also I've faced a strange problem
This ML is not for review requests.
Please read
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
best,
Joe
sent on the go
On Nov 14, 2013 4:26 AM, "Elena Ezhova" wrote:
> Hello all,
>
> I have made several patches that update modules in cinder/openstack/common
> fr
Random OSLO updates with no list of what changed, what got fixed etc
are unlikely to get review attention - doing such a review is
extremely difficult. I was -2ing them and asking for more info, but
they keep popping up. I'm really not sure what the best way of
updating from OSLO is, but this isn't
201 - 300 of 2874 matches
Mail list logo
