So, we can work around this in devstack, but it seems like there is a
more fundamental bug here that setup project isn't following dependencies.
Dep chain was: testtools (from
zake=0.1-tooz=0.12,=0.3-ceilometer==2014.2.3.dev2)
Unneeded _runtime_ dependency on testtools was removed in
Hi sahara folks,
We'll be having the Sahara team meeting tomorrow at #openstack-meeting-3
channel.
Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meetingiso=20150312T14
P.S. I'll be unavailable at this
Correction, Michael McCune (elmiko) will chair the meeting.
On Wed, Mar 11, 2015 at 3:57 PM, Sergey Lukjanov slukja...@mirantis.com
wrote:
Hi sahara folks,
We'll be having the Sahara team meeting tomorrow at #openstack-meeting-3
channel.
Agenda:
Regarding bug 1426046 (see below) -- Is this just a matter of making the
classes public or are you thinking the driver interface needs more
thought + solidifying before making something extendable?
Perhaps I can donate a cycle to 2 to help get this in.
On 2/26/15 10:33 AM, Doug Hellmann wrote:
Hello,
I would like to get a freeze exception for patch Correct initialization order
for logging to use eventlet locks, [0].
https://review.openstack.org/#/c/163387/
The bug fixed by the changeset is known to affect Keystone deployed with
eventlet. I am aware of a customer who hit this bug in
I'll keep it in mind not to create unnecessary backports, although I really
find it more convenient to do them once I submit changes to master for
review. I apologize for [4], it indeed was wrong and it won't happen again.
Regards,
Bartłomiej
On Wed, Mar 11, 2015 at 12:36 AM, Ryan Moe
Hi,
Just a quick update on where we are at with the release:
https://wiki.openstack.org/wiki/Kilo_Release_Schedule
Please help review all the code we want to merge before FeatureFreeze:
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking
https://launchpad.net/nova/+milestone/kilo-3
Ok, thanks Anne!
On Tue, Mar 10, 2015 at 6:10 PM, Anne Gentle annegen...@justwriteclick.com
wrote:
On Tue, Mar 10, 2015 at 3:35 PM, Erlon Cruz sombra...@gmail.com wrote:
Hi Anne,
Thanks for the quick answer. One thing that still not clear for me is
about the documentation that is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2015 12:21 PM, Alan Pevec wrote:
Hi,
next Icehouse stable point release 2014.1.4 has been slipping last
few weeks due to various gate issues, see Recently closed section
in https://etherpad.openstack.org/p/stable-tracker for details.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2015 12:51 PM, Boris Bobrov wrote:
Hello,
I would like to get a freeze exception for patch Correct
initialization order for logging to use eventlet locks, [0].
https://review.openstack.org/#/c/163387/
The bug fixed by the changeset
- Original Message -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Should we target it for Kilo? It does not seem right to allow it
slipping into the next release while we know there are operators
relying on the feature.
Of course, this will be fixed for Kilo.
This is the
+1 to what John said (overall).
However, I think I know where Erno is coming from. We're very close to the FF
and people are trying hard to get green on the check as well as ensure
thoroughness of the feature; this might lead to bunch of these errors.
Pointing them out and expecting to
When use_namespaces is True, there will be a namespace metadata proxy launched
for either dhcp or router namespace, this proxy will accept metada service
request , and then proxy the request to metadata server via metadata agent.
But when use_namespaces is False, there is no namespace metadata
On 11 March 2015 at 05:29, Russell Bryant rbry...@redhat.com wrote:
The TC is in the middle of implementing a fairly significant change in
project governance. You can find an overview from Thierry on the
OpenStack blog [1].
Part of the change is to recognize more projects as being part of
It sounds like we're diverging a bit from the original topic, but...
whatever.
Yeah! We should totally work towards a quota service - that's what we said
back in 2011
This is a topic that comes back regularly like the Halley's comet. With the
only difference that it happens every 6 months, not 75
On 11/03/15 19:06 +, Tim Bell wrote:
-Original Message-
From: Stefano Maffulli [mailto:stef...@openstack.org]
Sent: 11 March 2015 03:16
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Avoiding regression in project governance
On Tue, 2015-03-10 at 15:23 -0700,
-Original Message-
From: Stefano Maffulli [mailto:stef...@openstack.org]
Sent: 12 March 2015 00:26
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Avoiding regression in project governance
On Wed, 2015-03-11 at 17:59 -0500, Ed Leafe wrote:
The longer we try
Can you explain why are you not using namespaces? (I'm really curious).
I've been thinking of proposing to deprecate that option only for the simple
truth that it's not tested and we have no idea if it works anymore, or if anyone
actually uses it.
- Original Message -
When
hi,
sorry for keep forgetting and thank you for reminder.
YAMAMOTO Takashi
Hi-
Regarding the CI offline mails, I previously received an email from Anita.
Please find the summary below.
Please set your account listing to down on this page:
On 2015-03-10 23:00:16 + (+), Devananda van der Veen wrote:
Many of those requirements were subjective (well tested, well
documented, etc) and had to be evaluated by the TC. Are these the
sort of tags you're referring to? If so, and if the TC delegated
responsibility to manage the
On Wed, Mar 11, 2015 at 02:25:26PM +, Ian Cordasco wrote:
I have no opinions on the matter. Either 1400 or 1500 work for me. I think
there are a lot of people asking for it to be at 1500 instead though.
Would anyone object to changing it to 1500 instead (as long as it is one
consistent
On Wed, 11 Mar 2015, Matt Riedemann wrote:
Thanks for writing this up. Etherpads are usually a mess for those not
involved in creating them so it's always useful to have some summary and
digestion after the fact.
+trillion for summaries. Going to look at an etherpad is pretty much
useless
On Wed, 11 Mar 2015, Alan Pevec wrote:
So, we can work around this in devstack, but it seems like there is a
more fundamental bug here that setup project isn't following dependencies.
Dep chain was: testtools (from
zake=0.1-tooz=0.12,=0.3-ceilometer==2014.2.3.dev2)
Unneeded _runtime_
hi,
Ryu/ofagent CI will be offline during the next weekend
for a scheduled maintenance. sorry for inconvenience.
YAMAMOTO Takashi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi all
will instance action deprecate in feature since we have notify mechanism now?
Currently, nova have instance action and instance event action to record
specify actions performed on a instances.
For some enterprise user, they may need to compute the latency when they
perform an action on an
I have no opinions on the matter. Either 1400 or 1500 work for me. I think
there are a lot of people asking for it to be at 1500 instead though.
Would anyone object to changing it to 1500 instead (as long as it is one
consistent time for the meeting)?
On 3/11/15, 01:53, Inessa Vasilevskaya
On 3/11/2015 7:59 AM, Sean Dague wrote:
The last couple of days I was at the Operators Meetup acting as Nova
rep for the meeting. All the sessions were quite nicely recorded to
etherpads here - https://etherpad.openstack.org/p/PHL-ops-meetup
There was both a specific Nova session -
-- Forwarded message --
From: jacob jacob opstk...@gmail.com
Date: Tue, Mar 10, 2015 at 6:00 PM
Subject: PCI passthrough of 40G ethernet interface
To: openst...@lists.openstack.org
Hi,
I'm interested in finding out if anyone has successfully tested PCI
passthrough functionality
Hi Stefano,
Thanks so much for your detailed answer, I finally know the reason why those
patches are not reviewed in this cycle.
Actually, this BP
(https://blueprints.launchpad.net/python-cinderclient/+spec/support-modify-volume-image-metadata)
is created very
early around Nov. 2014, and
is there anyone tryed this and successfully?
On Mon, Mar 9, 2015 at 4:25 PM, Lei Zhang zhang.lei@gmail.com wrote:
Hi guys,
I am setting up the keytone v3 api. Now I meet a issue about the
`cloud_admin` policy.
Base on the
On 12 March 2015 at 13:18, Ian Wienand iwien...@redhat.com wrote:
On 03/12/2015 10:37 AM, Ian Wienand wrote:
File /tmp/easy_install-mV2rSm/unittest2-1.0.0/unittest2/case.py, line
16, in module
ImportError: cannot import name range
Complete output from command python setup.py
On Mar 12, 2015, at 04:08, Steven Dake (stdake) std...@cisco.com wrote:
On 3/10/15, 12:22 AM, Bohai (ricky) bo...@huawei.com wrote:
Hi, stackers
I try to use the Kolla Images and pull them down from docker hub.
I found the size of the image is bigger than what I thought(for
Oh, sure - switching to the spec is fine, I didn't realise there was
one, given the list thread had gone quiet :)
-Rob
On 12 March 2015 at 12:24, Ruby Loo rlooya...@gmail.com wrote:
On 11 March 2015 at 18:21, Robert Collins robe...@robertcollins.net wrote:
...
Since there was no debate on
On 12 March 2015 at 13:05, Salvatore Orlando sorla...@nicira.com wrote:
It sounds like we're diverging a bit from the original topic, but...
whatever.
Yeah! We should totally work towards a quota service - that's what we said
back in 2011
:).
This is a topic that comes back regularly like
On Wed, Mar 11, 2015 at 8:17 PM, Chen, Wei D wei.d.c...@intel.com wrote:
Hi Stefano,
Thanks so much for your detailed answer, I finally know the reason why
those patches are not reviewed in this cycle.
Actually, this BP (
101 - 135 of 135 matches
Mail list logo
