- Original Message -
What's the progress by Terry Wilson?
If not much, I'm willing to file blueprint/spec and drive it.
thanks,
I've been working on some proof-of-concept code to help flesh out ideas for
writing the spec. I'd talked to Maru and he mentioned that he didn't think
A question about the fix from https://review.openstack.org/#/c/82931
Also, how does this work for RHEL-based distros where they tend to backport
new kernel features? For instance vxlan support was added in the kernel for
RHEL6.5 which is 2.6.32-based... That changeset looks like it breaks
Sorry, I dropped the ball here. This is now released.
Unfortunately, the new novaclient release ended up completely breaking the
neutron gate. The v1_1 deprecation broke our (voting) pylint test:
https://jenkins04.openstack.org/job/gate-neutron-pylint/1383/console
2015-02-19 18:37:06.932 |
- Original Message -
On Feb 19, 2015, at 11:52, Terry Wilson twil...@redhat.com wrote:
Unfortunately, the new novaclient release ended up completely breaking the
neutron gate. The v1_1 deprecation broke our (voting) pylint test:
https://jenkins04.openstack.org/job/gate-neutron
Right now I'm leaning toward parent always does nothing + PluginWorker.
Everything is forked, no special case for workers==0, and explicit
designation of the only one case. Of course, it's still early in the day
and I haven't had any coffee.
I have updated the patch
There are two classes of behavior that need to be handled:
1) There are things that can only be done after forking like setting up
connections or spawning threads.
2) Some things should only be done once regardless of number of forks, like
syncing.
Even when you just want something to happen
> So basically, as long as we try to plug ports with different MTUs into the
> same bridge, we are utilizing a bug in Open vSwitch, that may break us any
> time.
>
> I guess our alternatives are:
> - either redesign bridge setup for openvswitch to e.g. maintain a bridge per
> network;
> - or
On Tue, Jul 26, 2016 at 10:04 AM, Jakub Libosvar wrote:
> On 26/07/16 16:56, Assaf Muller wrote:
>>
>> We've hit critical mass from cores interesting in the testing area.
>>
>> Welcome Jakub to the core reviewer team. May you enjoy staring at the
>> Gerrit interface and
+1
On Mon, Feb 20, 2017 at 12:57 PM, Lihi Wish wrote:
> +1
>
> On Feb 20, 2017 1:13 PM, "Omer Anson" wrote:
>>
>> +1
>>
>> On 20 February 2017 at 19:34, Bhatia, Manjeet S
>> wrote:
>>>
>>> +1
>>>
>>>
>>>
>>> From: Kevin Benton
+1
On Feb 17, 2017 1:22 PM, "Kevin Benton" wrote:
> Hi all,
>
> I'm organizing a Neutron social event for Thursday evening in Atlanta
> somewhere near the venue for dinner/drinks. If you're interested, please
> reply to this email with a "+1" so I can get a general count for a
On Wed, Jun 10, 2015 at 4:41 AM, Robert Collins
wrote:
> On 10 June 2015 at 21:30, Ihar Hrachyshka wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 06/10/2015 02:15 AM, Robert Collins wrote:
>>> I'm very glad folk are working
On Sep 13, 2016 10:42 PM, "Kevin Benton" wrote:
>
> >All performance matters. All memory consumption matters. Being wasteful
over a purely aesthetic few extra characters of code is silly.
>
> Isn't the logical conclusion of this to write everything in a different
language? :)
On Thu, Jun 11, 2015 at 8:33 AM, Sean Dague wrote:
> On 06/11/2015 09:02 AM, Jay Pipes wrote:
>> On 06/11/2015 01:16 AM, Robert Collins wrote:
>>> But again - where in OpenStack does this matter the slightest?
>>
>> Precisely. I can't think of a single case where we are iterating
On Tue, Sep 13, 2016 at 6:31 PM, Jay Pipes <jaypi...@gmail.com> wrote:
> On 09/13/2016 01:40 PM, Terry Wilson wrote:
>>
>> On Thu, Jun 11, 2015 at 8:33 AM, Sean Dague <s...@dague.net> wrote:
>>>
>>> On 06/11/2015 09:02 AM, Jay Pipes wrote:
>>&
+1
On Tue, Sep 12, 2017 at 6:23 PM, Miguel Lavalle wrote:
> Dear Neutrinos,
>
> Our social event will take place on Thursday September 12th at 7:30pm. The
> venue is going to be https://www.famousdaves.com/Denver-Stapleton. It is
> located 0.4 miles from the Renaissance
ovsdbapp 0.9.1 (review https://review.openstack.org/#/c/539489/) has a
gate-fixing one-line fix (https://review.openstack.org/#/c/537241).
Can I get a FFE for bumping the requirements to ovsdbapp 0.9.1 once
the package is built?
Terry
On Fri, Feb 2, 2018 at 4:30 PM, Matthew Thode <prometheanf...@gentoo.org> wrote:
> On 18-02-02 15:59:42, Terry Wilson wrote:
>> ovsdbapp 0.9.1 (review https://review.openstack.org/#/c/539489/) has a
>> gate-fixing one-line fix (https://review.openstack.org/#/c/537241
17 matches
Mail list logo