I think these inconsistencies are valid bugs, in fact for volume names a
proposed fix has been merged yet:
https://bugs.launchpad.net/horizon/+bug/1389172
For image name there is a report for this kind of bug:
https://bugs.launchpad.net/horizon/+bug/1420809 I am anyway not sure if
it is being work
Hi Robert,
Thanks for all your work in Ironic.
Cheers,
Lucas
On Wed, Feb 25, 2015 at 12:25 AM, Robert Collins
wrote:
> Like with TripleO, I've not been pulling my weight as a core reviewer
> for a bit; I'd be very hesitant to +A in the project as a result.
>
> I'm still very interested in Ironi
Robert Collins wrote:
>> It's also worth noting that we were on a 3-month cycle at the start of
>> OpenStack. That was dropped after a cataclysmic release that managed the
>> feat of (a) not having anything significant done, and (b) have out of
>> date documentation and translations.
>
> Oh!
> ht
On Tue, Feb 24, 2015 at 10:02:36PM -0800, Mark Atwood wrote:
> On Tue, Feb 24, 2015, at 04:28, Kashyap Chamarthy wrote:
> >
> > Along with the below, if push comes to shove, OpenStack Foundation could
> > probably try a milder variant (obviously, not all activities can be
> > categorized as 'criti
On Wed, Feb 25, 2015 at 10:31:58AM +0100, Thierry Carrez wrote:
> Robert Collins wrote:
> >> It's also worth noting that we were on a 3-month cycle at the start of
> >> OpenStack. That was dropped after a cataclysmic release that managed the
> >> feat of (a) not having anything significant done, an
+1 to separate monolithic OVN plugin
The ML2 has been designed for co-existing of multiple heterogeneous
backends, it works well for all agent solutions: OVS, Linux Bridge, and
even ofagent.
However, when things come with all kinds of agentless solutions, especially
all kinds of SDN controller (e
Hi,
> I also just put up another proposal to consider:
> https://review.openstack.org/#/c/156711/
> """Sew over eventlet + patching with threads"""
My asyncio spec is unclear about WSGI, I just wrote
"The spec doesn't change OpenStack components running WSGI servers
like nova-api. The specific p
On 02/24/2015 05:38 PM, Kevin Benton wrote:
> OVN implementing it's own control plane isn't a good reason to make it a
> monolithic plugin. Many of the ML2 drivers are for technologies with
> their own control plane.
>
> Going with the monolithic plugin only makes sense if you are certain
> that y
The only thing I'd argue with here is the log level, Robert. Logstash on
the gate doesn't index trace/debug, so info or above would be far more
helpful, so that we can have a logstash query for the issue
On 25 February 2015 at 01:20, Robert Collins
wrote:
> On 23 February 2015 at 13:54, Michael
On Wed, Feb 25, 2015 at 5:34 AM, Sukhdev Kapur
wrote:
> Folks,
>
> A great discussion. I am not expert at OVN, hence, want to ask a question.
> The answer may make a case that it should probably be a ML2 driver as
> oppose to monolithic plugin.
>
> Say a customer want to deploy an OVN based solu
Hi,
I see the below error in my devstack and is raised from the package 'six'
AttributeError: 'Module_six_moves_urllib_parse' object has no attribute
'SplitResult'
Currently my devstack setup is having six 1.9.0 version. Could anyone help here
to fix the issue? Thanks.
Regards
Kanagaraj M
___
Hi
You probably have an old python-six version installed system-wide.
Jordan
On Wed, Feb 25, 2015 at 11:56 AM, Manickam, Kanagaraj <
[email protected]> wrote:
> Hi,
>
>
>
> I see the below error in my devstack and is raised from the package ‘six’
>
>
>
> AttributeError: 'Module_six_move
Normally “apt-get remove python-six” helps.
From: Jordan Pittier [mailto:[email protected]]
Sent: Wednesday, February 25, 2015 12:08 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Module_six_moves_urllib_parse error
Hi
You probably have a
Thanks Michal. It helped me to get rid of the issue.
From: Dulko, Michal [mailto:[email protected]]
Sent: Wednesday, February 25, 2015 4:49 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Module_six_moves_urllib_parse error
Normally “apt-get r
On Wed, Feb 25, 2015 at 6:11 AM, Jeremy Stanley wrote:
> On 2015-02-25 01:02:07 +0530 (+0530), Bharat Kumar wrote:
> [...]
> > After running 971 test cases VM inaccessible for 569 ticks
> [...]
>
> Glad you're able to reproduce it. For the record that is running
> their 8GB performance flavor wit
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+Meeting&iso=20150226T14
--
Sincerely yours,
Sergey Luk
On 2015-02-24 22:06:32 -0600 (-0600), Chris Friesen wrote:
[...]
> Taking it as a dig, sometimes people just have their one itch to
> scratch and the rest of the project is "good enough" for them, and
> I think that's actually okay.
Not intended as a dig at anyone... just a subtle reminder that th
On 02/23/2015 03:18 PM, Matthew Booth wrote:
On 23/02/15 12:13, Gary Kotton wrote:
On 2/23/15, 2:05 PM, "Matthew Booth" wrote:
On 20/02/15 11:48, Matthew Booth wrote:
Gary Kotton came across a doozy of a bug recently:
https://bugs.launchpad.net/nova/+bug/1419785
In short, when you start
On Tue, Feb 24, 2015 at 04:19:39PM +0100, Markus Zoeller wrote:
> Sahid Orentino Ferdjaoui wrote on 02/23/2015
> 11:13:12 AM:
>
> > From: Sahid Orentino Ferdjaoui
> > To: "OpenStack Development Mailing List (not for usage questions)"
> >
> > Date: 02/23/2015 11:17 AM
> > Subject: Re: [opensta
Although we are past the non-priority deadline, I have been encouraged
to request this late exception for Project Calico's spec and code adding
VIF_TYPE_TAP to Nova.
https://review.openstack.org/#/c/130732/ (spec)
https://review.openstack.org/#/c/146914/ (code)
Why might you consider this?
- It
On Wed, Feb 25, 2015 at 11:46:05AM +, Neil Jerram wrote:
> Although we are past the non-priority deadline, I have been encouraged
> to request this late exception for Project Calico's spec and code adding
> VIF_TYPE_TAP to Nova.
I'm afraid you're also past the freeze exception request deadline
Hi Michal,
> 1. Need of distributed lock to avoid same task being resumed by two instances
> of a service. Do we need tooz to do that or is there any other solution?
Tooz library is already being used in ceilometer to manage group membership.
(https://github.com/openstack/ceilometer/blob/master
Thanks for putting this all together, Salvatore.
I just want to comment on this suggestion:
> 1) Move the allocation logic out of the driver, thus making IPAM an
independent service. The API workers will then communicate with the IPAM
service through a message bus, where IP allocation requests wil
On 2015-02-25 17:02:34 +0530 (+0530), Deepak Shetty wrote:
[...]
> Run 2) We removed glusterfs backend, so Cinder was configured with
> the default storage backend i.e. LVM. We re-created the OOM here
> too
>
> So that proves that glusterfs doesn't cause it, as its happening
> without glusterfs to
Excerpts from Salvatore Orlando's message of 2015-02-23 04:07:38 -0800:
> Lazy-Stacker summary:
> I am doing some work on Neutron IPAM code for IP Allocation, and I need to
> found whether it's better to use db locking queries (SELECT ... FOR UPDATE)
> or some sort of non-blocking algorithm.
> Some
On 02/25/2015 03:16 AM, Ajay Kalambur (akalambu) wrote:
> Hi
> I am trying to just get started with openstack commits and wanted to
> start by fixing some documentation bugs. I assigned 3 bugs which seem to
> be in the same file/area
Welcome!
Let's discuss this on the openstack-docs mailing list
Excerpts from Victor Stinner's message of 2015-02-25 02:12:05 -0800:
> Hi,
>
> > I also just put up another proposal to consider:
> > https://review.openstack.org/#/c/156711/
> > """Sew over eventlet + patching with threads"""
>
> My asyncio spec is unclear about WSGI, I just wrote
>
> "The spec
I’m writing a plan/script to benchmark OVS+OF(CT) vs OVS+LB+iptables+ipsets,
so we can make sure there’s a real difference before jumping into any
OpenFlow security group filters when we have connection tracking in OVS.
The plan is to keep all of it in a single multicore host, and make all the
Hi,
There is an issue with the statistics reported when a nova compute driver has
shared storage attached. That is, there may be more than one compute node
reporting on the shared storage. A patch has been posted -
https://review.openstack.org/#/c/155184. The direction here was to add a extra
p
Hi, stackers!
As was suggested in topic [1], using an HTTP header was a good solution for
communicating common/standardized OpenStack API error codes.
So I’d like to begin working on a common library, which will collect all
openstack HTTP API errors, and assign them string error codes. My suggest
On 25/02/15 11:51, Radoslav Gerganov wrote:
> On 02/23/2015 03:18 PM, Matthew Booth wrote:
>> On 23/02/15 12:13, Gary Kotton wrote:
>>>
>>>
>>> On 2/23/15, 2:05 PM, "Matthew Booth" wrote:
>>>
On 20/02/15 11:48, Matthew Booth wrote:
> Gary Kotton came across a doozy of a bug recently:
On Wed, Feb 25, 2015 at 7:52 AM, Miguel Ángel Ajo
wrote:
> I’m writing a plan/script to benchmark OVS+OF(CT) vs
> OVS+LB+iptables+ipsets,
> so we can make sure there’s a real difference before jumping into any
> OpenFlow security group filters when we have connection tracking in OVS.
>
> The pla
On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote:
> Hi,
> There is an issue with the statistics reported when a nova compute
> driver has shared storage attached. That is, there may be more than
> one compute node reporting on the shared storage. A patch has been
> posted - https://revie
On Wednesday, 25 de February de 2015 at 15:38, Kyle Mestery wrote:
> On Wed, Feb 25, 2015 at 7:52 AM, Miguel Ángel Ajo (mailto:[email protected])> wrote:
> > I’m writing a plan/script to benchmark OVS+OF(CT) vs
> > OVS+LB+iptables+ipsets,
> > so we can make sure there’s a real difference befo
On Wed, Feb 25, 2015 at 8:49 AM, Miguel Ángel Ajo
wrote:
> On Wednesday, 25 de February de 2015 at 15:38, Kyle Mestery wrote:
>
> On Wed, Feb 25, 2015 at 7:52 AM, Miguel Ángel Ajo
> wrote:
>
> I’m writing a plan/script to benchmark OVS+OF(CT) vs
> OVS+LB+iptables+ipsets,
> so we can make sure t
On Wed, Feb 25, 2015 at 6:34 PM, Jeremy Stanley wrote:
> On 2015-02-25 17:02:34 +0530 (+0530), Deepak Shetty wrote:
> [...]
> > Run 2) We removed glusterfs backend, so Cinder was configured with
> > the default storage backend i.e. LVM. We re-created the OOM here
> > too
> >
> > So that proves th
On 02/25/2015 08:52 AM, Miguel Ángel Ajo wrote:
> I’m writing a plan/script to benchmark OVS+OF(CT) vs OVS+LB+iptables+ipsets,
> so we can make sure there’s a real difference before jumping into any
> OpenFlow security group filters when we have connection tracking in OVS.
>
> The plan is to keep
Thanks Clint.
I think you are bringing an interesting and disruptive perspective into
this discussion.
Disruptive because one thing that has not been considered so far in this
thread is that perhaps we don't need at all to leverage multi-master
capabilities for write operations.
More comments inl
jOn Mon, Feb 23, 2015 at 5:07 AM, Salvatore Orlando wrote:
> Lazy-Stacker summary:
> I am doing some work on Neutron IPAM code for IP Allocation, and I need to
> found whether it's better to use db locking queries (SELECT ... FOR UPDATE)
> or some sort of non-blocking algorithm.
> Some measures su
On 25 February 2015 at 13:50, Eugene Nikanorov
wrote:
> Thanks for putting this all together, Salvatore.
>
> I just want to comment on this suggestion:
> > 1) Move the allocation logic out of the driver, thus making IPAM an
> independent service. The API workers will then communicate with the IPA
Hi Robert,
I'm really glad I had a chance to interact with you. Thanks for everything;
I'm hopeful that we'll see you back.
Ironic still has lots of life, so I guess life goes on without lifeless,
but I'll miss you still. ;)
--ruby
On 25 February 2015 at 02:35, Robert Collins
wrote:
> On 24 February 2015 at 01:07, Salvatore Orlando
> wrote:
> > Lazy-Stacker summary:
> ...
> > In the medium term, there are a few things we might consider for
> Neutron's
> > "built-in IPAM".
> > 1) Move the allocation logic out of the driver,
On 2/25/15, 10:52 AM, "Carl Baldwin" wrote:
>
>Wondering if Kilo should just focus on creating the interface which
>will allow us to create multiple implementations and swap them out
>during the Liberty development cycle. Hopefully, this could include
>even something like your option 2 below.
>
Hi,
I was wondering what people thought about patches that only fix grammatical
issues or misspellings in comments in our code.
I can't believe I'm sending out this email, but as a group, I'd like it if
we had a similar understanding so that we treat all patches in a similar
(dare I say it, cons
The Oslo team is thrilled to announce the release of:
oslo.messaging 1.7.0: Oslo Messaging API
For more details, please see the git log history below and:
http://launchpad.net/oslo.messaging/+milestone/1.7.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo.messag
Hi Eugeniya,
Please have a look on the discussion under tag [log]. We’ve been discussing
around this topic (bit wider, not limiting to API errors) quite regular since
Paris Summit and we should have X-project specs for review quite soon after the
Ops meetup. The workgroup meetings will start as
On 25 February 2015 at 16:52, Carl Baldwin wrote:
> jOn Mon, Feb 23, 2015 at 5:07 AM, Salvatore Orlando
> wrote:
> > Lazy-Stacker summary:
> > I am doing some work on Neutron IPAM code for IP Allocation, and I need
> to
> > found whether it's better to use db locking queries (SELECT ... FOR
> UP
>From previous discussion, it appeared the proposer really felt this needed
to be a "core" neutron aspect.
Where by "core" they meant both be part of the core API and part of
openstack/neutron.
On the other hand, we also agreed that the best way forward was to develop
a service plugin which in a w
On Wed, Feb 25, 2015, at 09:33 AM, Eugeniya Kudryashova wrote:
> Hi, stackers!
>
> As was suggested in topic [1], using an HTTP header was a good solution
> for
> communicating common/standardized OpenStack API error codes.
>
> So I’d like to begin working on a common library, which will collec
Hi Tim, All,
1) Step 3: The VM-placement engine is also a "datalog engine" . Right?
When policies are delegated:
when policies are inserted? When the VM-placement engine has already registered
itself all policies are given to it?
"In our example, this would mean the domain-specific pol
Ruby Loo said on Wed, Feb 25, 2015 at 11:26:56AM -0500:
> I was wondering what people thought about patches that only fix grammatical
> issues or misspellings in comments in our code.
For my money, a patch fixing nits has value but only if it fixes a few.
If it's a follow-up patch it should fix al
On 02/25/2015 05:52 AM, Miguel Ángel Ajo wrote:
I’m writing a plan/script to benchmark OVS+OF(CT) vs
OVS+LB+iptables+ipsets,
so we can make sure there’s a real difference before jumping into any
OpenFlow security group filters when we have connection tracking in OVS.
The plan is to keep all of i
On 02/25/2015 05:26 PM, Ruby Loo wrote:
Hi,
I was wondering what people thought about patches that only fix
grammatical issues or misspellings in comments in our code.
I can't believe I'm sending out this email, but as a group, I'd like it
if we had a similar understanding so that we treat all
[Parse the subject as new-meeting time, as there is no old meeting time...]
OpenStackClient will start holding periodic development team meetings on
Thursday Feb 26 at 18:00 UTC in Freenode's #openstack-meeting channel. One
of the first things I want to cover is timing and frequency of these
meet
> On Feb 25, 2015, at 10:26 AM, Ruby Loo wrote:
>
> Hi,
>
> I was wondering what people thought about patches that only fix grammatical
> issues or misspellings in comments in our code.
>
> I can't believe I'm sending out this email, but as a group, I'd like it if we
> had a similar underst
On Wed, Feb 25, 2015 at 8:42 PM, Deepak Shetty wrote:
>
>
> On Wed, Feb 25, 2015 at 6:34 PM, Jeremy Stanley wrote:
>
>> On 2015-02-25 17:02:34 +0530 (+0530), Deepak Shetty wrote:
>> [...]
>> > Run 2) We removed glusterfs backend, so Cinder was configured with
>> > the default storage backend i.e
On Tue, Feb 24, 2015, Jeremy Stanley wrote:
> On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
> [...]
> > Recently, I have spent a lot more time waiting on reviews than I
> > have spent writing the actual code.
>
> That's awesome, assuming what you mean here is that you've spent
> m
Not sure where it disappeared, but there are none of the API pages for
VPNaaS exist. This was added some time ago (I think it was review 41702
back in 9/2013).
Mentioned to Edgar, but wanted to let the community know...
PCM (Paul Michali)
IRC pc_m (irc.freenode.com)
Twitter...
\o/
I'll be there! Thanks for organizing it all Dean.
Steve
Dean Troyer wrote on 02/25/2015 12:19:38 PM:
> From: Dean Troyer
> To: OpenStack Development Mailing List
> Date: 02/25/2015 12:32 PM
> Subject: [openstack-dev] [OpenStackClient] New meeting time
>
> [Parse the subject as new-meet
As you can see, netconn-api has gone into the Openstack-attic.
A few months ago, all neutron API reference docs were moved into
neutron-specs (similar things happened to other projects).
The new home of the VPN API spec is [1]
Salvatore
[1]
http://specs.openstack.org/openstack/neutron-specs/spec
Sahid Orentino Ferdjaoui wrote on 02/25/2015
12:58:30 PM:
> [...]
>
> So we probably have a bug here, can you at least refer it in launchpad
> ? We need to see if the problem comes from the code in Nova or a bad
> interpretation of the behavior of libvirt or a bug in libvirt.
>
> Please on the
Hi
So a review [1] was recently submitted to cinder to fix up all of the H302
violations, and turn on the automated check for them. This is certainly a
reasonable suggestion given the number of manual reviews that -1 for this
issue, however I'm far from convinced it actually makes the code more
re
On Wed, Feb 25, 2015 at 10:51 AM, Duncan Thomas
wrote:
> Hi
>
> So a review [1] was recently submitted to cinder to fix up all of the H302
> violations, and turn on the automated check for them. This is certainly a
> reasonable suggestion given the number of manual reviews that -1 for this
> issu
Thanks for that, Joe. I'd say the cons miss 'It looks ugly in places'.
On 25 February 2015 at 20:54, Joe Gordon wrote:
>
> On Wed, Feb 25, 2015 at 10:51 AM, Duncan Thomas
> wrote:
>
>> Hi
>>
>> So a review [1] was recently submitted to cinder to fix up all of the
>> H302 violations, and turn on
Hi,
The RFC2544 with near zero packet loss is a pretty standard performance
benchmark. It is also used in the OPNFV project (
https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases
).
Does this mean that OpenStack will have stateful firewalls (or security
groups)? Any oth
The fact that a system doesn't use a neutron agent is not a good
justification for monolithic vs driver. The VLAN drivers co-exist with OVS
just fine when using VLAN encapsulation even though some are agent-less.
There is a missing way to coordinate connectivity with tunnel networks
across drivers
During yesterday’s cross-project meeting [1], we discussed the "Eventlet Best
Practices” spec [2] started by bnemec. The discussion of that spec revolved
around the question of whether our cross-project specs repository is the right
place for this type of document that isn’t a “plan” for a chang
On Feb 25, 2015, at 10:51, Duncan Thomas wrote:
> Is there anybody who'd like to step forward in defence of this rule and
> explain why it is an improvement? I don't discount for a moment the
> possibility I'm missing something, and welcome the education in that case
A reason I can think of wo
On 26 February 2015 at 08:54, melanie witt wrote:
> On Feb 25, 2015, at 10:51, Duncan Thomas wrote:
>
>> Is there anybody who'd like to step forward in defence of this rule and
>> explain why it is an improvement? I don't discount for a moment the
>> possibility I'm missing something, and welco
Hi, fuelers,
As you may know, we have a rich and complex network_transformations section
in astute.yaml. We use it to describe which OVS/Linux network primitives
should be created and how they should be connected together. This section
is used by "l23network" Puppet module during the deployment st
On Wed, Feb 25, 2015 at 12:59 PM, Robert Collins
wrote:
> On 26 February 2015 at 08:54, melanie witt wrote:
> > On Feb 25, 2015, at 10:51, Duncan Thomas
> wrote:
> >
> >> Is there anybody who'd like to step forward in defence of this rule and
> explain why it is an improvement? I don't discount
Yeah, it seems ML2 at the least should save you a lot of boilerplate.
On Feb 25, 2015 2:32 AM, "Russell Bryant" wrote:
> On 02/24/2015 05:38 PM, Kevin Benton wrote:
> > OVN implementing it's own control plane isn't a good reason to make it a
> > monolithic plugin. Many of the ML2 drivers are for
On Fri, Feb 20, 2015 at 3:48 AM, Matthew Booth wrote:
> Gary Kotton came across a doozy of a bug recently:
>
> https://bugs.launchpad.net/nova/+bug/1419785
>
> In short, when you start a Nova compute, it will query the driver for
> instances and compare that against the expected host of the the i
On Wed, Feb 25, 2015 at 11:54 AM, Doug Hellmann
wrote:
> During yesterday’s cross-project meeting [1], we discussed the "Eventlet
> Best Practices” spec [2] started by bnemec. The discussion of that spec
> revolved around the question of whether our cross-project specs repository
> is the right p
On Wed, Feb 25, 2015, at 12:36 PM, Jay Faulkner wrote:
>
> > On Feb 25, 2015, at 10:26 AM, Ruby Loo wrote:
> >
> > Hi,
> >
> > I was wondering what people thought about patches that only fix grammatical
> > issues or misspellings in comments in our code.
> >
> > I can't believe I'm sending
On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell wrote:
>
> A few inline comments and a general point
>
> How do we handle scenarios like volumes when we have a per-component
> janitor rather than a single co-ordinator ?
>
> To be clean,
>
> 1. nova should shutdown the instance
> 2. nova should then ask
On Wed, Feb 25, 2015, at 12:35 PM, Johannes Erdfelt wrote:
> On Tue, Feb 24, 2015, Jeremy Stanley wrote:
> > On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
> > [...]
> > > Recently, I have spent a lot more time waiting on reviews than I
> > > have spent writing the actual code.
>
https://pypi.python.org/pypi/sqlalchemy-migrate/0.9.5
Changes:
mriedem@ubuntu:~/git/sqlalchemy-migrate$ git log --oneline --no-merges
0.9.4..0.9.5
5feeaba Don't run the test if _setup() fails
c8c5c4b Correcting minor typo
9d212e6 Fix .gitignore for .tox and .testrepository
ae64d82 allow droppi
Ditto!
On Wed, Feb 25, 2015, at 01:35 PM, Steve Martinelli wrote:
> \o/
>
> I'll be there! Thanks for organizing it all Dean.
>
> Steve
>
> Dean Troyer wrote on 02/25/2015 12:19:38 PM:
>
> > From: Dean Troyer
> > To: OpenStack Development Mailing List
>
> > Date: 02/25/2015 12:32 PM
> > Su
Tom Fifield wrote on 25/02/2015 06:46:13 AM:
> On 24/02/15 19:27, Daniel P. Berrange wrote:
> > On Tue, Feb 24, 2015 at 12:05:17PM +0100, Thierry Carrez wrote:
> >> Daniel P. Berrange wrote:
> >>> [...]
>
> > I'm not familiar with how the translations works, but if they are
> > waiting until the
Excerpts from Duncan Thomas's message of 2015-02-25 10:51:00 -0800:
> Hi
>
> So a review [1] was recently submitted to cinder to fix up all of the H302
> violations, and turn on the automated check for them. This is certainly a
> reasonable suggestion given the number of manual reviews that -1 for
On Wed, Feb 25, 2015, at 02:59 PM, Robert Collins wrote:
> On 26 February 2015 at 08:54, melanie witt wrote:
> > On Feb 25, 2015, at 10:51, Duncan Thomas wrote:
> >
> >> Is there anybody who'd like to step forward in defence of this rule and
> >> explain why it is an improvement? I don't disco
On Wed, Feb 25, 2015, at 03:14 PM, Joe Gordon wrote:
> On Wed, Feb 25, 2015 at 11:54 AM, Doug Hellmann
> wrote:
>
> > During yesterday’s cross-project meeting [1], we discussed the "Eventlet
> > Best Practices” spec [2] started by bnemec. The discussion of that spec
> > revolved around the ques
Clint
This rule is not currently enabled in Cinder. This review fixes up all
cases and enables it, which is absolutely 100% the right thing to do if we
decide to implement this rule.
The purpose of this thread is to understand the value of the rule. We
should either enforce it, or else explicitly
On Wed, Feb 25, 2015 at 12:49 PM, Doug Hellmann
wrote:
>
>
> On Wed, Feb 25, 2015, at 03:14 PM, Joe Gordon wrote:
> > On Wed, Feb 25, 2015 at 11:54 AM, Doug Hellmann
> > wrote:
> >
> > > During yesterday’s cross-project meeting [1], we discussed the
> "Eventlet
> > > Best Practices” spec [2] sta
Wondering if heat should be performing this orchestration.
Would provide for a more pluggable front end to the action set.
-matt
On Feb 25, 2015 2:37 PM, Joe Gordon wrote:
>
>
>
> On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell wrote:
>>
>>
>> A few inline comments and a general point
>>
>> How do w
On Tue, Feb 24, 2015 at 7:00 AM, Doug Hellmann
wrote:
>
>
> On Mon, Feb 23, 2015, at 06:31 PM, Joe Gordon wrote:
> > On Mon, Feb 23, 2015 at 11:04 AM, Doug Hellmann
> > wrote:
> >
> > >
> > >
> > > On Mon, Feb 23, 2015, at 12:26 PM, Joe Gordon wrote:
> > > > On Mon, Feb 23, 2015 at 8:49 AM, Ihar
Cool! Glad to see it is not gone. Should it also be on the API reference
pages?
http://developer.openstack.org/api-ref-networking-v2.html
PCM (Paul Michali)
IRC pc_m (irc.freenode.com)
Twitter... @pmichali
On Wed, Feb 25, 2015 at 1:42 PM, Salvatore Orlando
wrote:
> As you can
On Wed, Feb 25, 2015, at 04:04 PM, Joe Gordon wrote:
> On Tue, Feb 24, 2015 at 7:00 AM, Doug Hellmann
> wrote:
>
> >
> >
> > On Mon, Feb 23, 2015, at 06:31 PM, Joe Gordon wrote:
> > > On Mon, Feb 23, 2015 at 11:04 AM, Doug Hellmann
> > > wrote:
> > >
> > > >
> > > >
> > > > On Mon, Feb 23, 201
On 2/25/15, 14:41, "Doug Hellmann" wrote:
>
>
>On Wed, Feb 25, 2015, at 12:35 PM, Johannes Erdfelt wrote:
>> On Tue, Feb 24, 2015, Jeremy Stanley wrote:
>> > On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
>> > [...]
>> > > Recently, I have spent a lot more time waiting on reviews
On Wed, Feb 25, 2015 at 3:11 PM, Paul Michali wrote:
> Cool! Glad to see it is not gone. Should it also be on the API reference
> pages?
>
> http://developer.openstack.org/api-ref-networking-v2.html
>
>
Yes, we've had a doc bug since last fall about it being missing from the
API Reference.
https
Jay,
I can only confirm your point of view.
I personally landed such a patch yesterday and saw it as an easy way to get
familiar with Gerrit.
My goal being to land some more complex patches in the near future.
Bernard
On Wed, Feb 25, 2015 at 12:37 PM, Doug Hellmann
wrote:
>
>
> On Wed, Feb 25,
Hi stackers,
When we started Rally we have a just small idea to make some tool that
generates load and measures performance. During almost 2 years a lot of
changed in Rally, so now it's quite common testing framework that allows to
cover various topics like: stress, load, volume, performance, neg
On 02/25/2015 02:54 PM, Doug Hellmann wrote:
During yesterday’s cross-project meeting [1], we discussed the "Eventlet Best
Practices” spec [2] started by bnemec. The discussion of that spec revolved around
the question of whether our cross-project specs repository is the right place for
this t
We've unwound the gate quite a bit, so the cost of extra patches in the
merge queue fixing trivial things (like comment spelling) is pretty low.
Honestly, I'd much rather merge functional fixes faster and not go an
extra 2 rounds of typo fixing (assuming the English is decipherable),
and merge typ
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, February 26th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome t
The “making things more explicit” argument carried to its logical
conclusion would require that no “import … as …” ever be used either, and
we would have to use the full namespace/path for each module or function
being used. With allowing “import … as …” and the practice of extending
and monkey pa
Excerpts from Duncan Thomas's message of 2015-02-25 12:51:35 -0800:
> Clint
>
> This rule is not currently enabled in Cinder. This review fixes up all
> cases and enables it, which is absolutely 100% the right thing to do if we
> decide to implement this rule.
>
> The purpose of this thread is to
On Wed, Feb 25, 2015 at 3:02 PM, Matt Joyce wrote:
> Wondering if heat should be performing this orchestration.
>
I wouldn't expect heat to have access to everything that needs to be
cleaned up.
>
> Would provide for a more pluggable front end to the action set.
>
> -matt
>
> On Feb 25, 2015 2
On 26 February 2015 at 05:26, Ruby Loo wrote:
> Hi,
>
> I was wondering what people thought about patches that only fix grammatical
> issues or misspellings in comments in our code.
>
> I can't believe I'm sending out this email, but as a group, I'd like it if
> we had a similar understanding so
1 - 100 of 118 matches
Mail list logo
