to speed?
>
> Cheers,
> Armando
>
> [1] https://review.openstack.org/#/c/411263/
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.
On Mon, Oct 24, 2016 at 7:39 AM, Das, Anindita wrote:
> 1. https://bugs.launchpad.net/neutron/+bug/1635554 - Delete Router /
> race condition
>
I've triaged this bug and assigned it to myself. I'll make sure this
either gets solved or gets the proper attention.
--
J
t; __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
tests, logic or
infra that involve these tests will need to prove that they actually
work downstream.
We are now open for ideas about this idea.
[1]: https://en.wikipedia.org/wiki/IEEE_802.1Q
--
John Schwarz,
Senior Software Engineer,
Red Hat.
_
on
Tuesday.
[1]: http://www.gourmetburgerbistro.ie/
[2]: https://etherpad.openstack.org/p/newton-neutron-midcycle
See you then,
--
John Schwarz,
Red Hat.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
cluster configuration? I
> can't quite tell from the doc.
>
> On Fri, Jul 22, 2016 at 12:58 AM, John Schwarz wrote:
>>
>> You're right Joshua.
>>
>> Tooz HEAD points to 0f4e1198fdcbd6a29d77c67d105d201ed0fbd9e0.
>>
>> With regards to etcd and z
> Hi John,
>
> Thanks for gathering this info,
>
> Do you have the versions of the backend that were used here (particularly
> relevant for etcd which has a new release pretty frequently).
>
> It'd be useful to capture that info also :)
>
> John Schwarz wrote:
>>
&
ended the Austin Summit meeting and other
interested parties)
Happy locking,
[1]: http://lists.openstack.org/pipermail/openstack-dev/2016-April/093199.html
[2]:
https://docs.google.com/document/d/1jdI8gkQKBE0G9koR0nLiW02d5rwyWv_-gAp7yavt4w8
[3]: https://review.openstack.org/#/c/342096/
--
John Sch
-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://list
speak with Kobi Samoray - he implemented this for the
>> vmware_nsx repository using tooz. Its pretty cool.
>> Thanks
>> Gary
>>
>>
>>
>>
>> On 4/23/16, 5:16 PM, "John Schwarz" wrote:
>>
>>> Hi guys,
>>>
>>>
+1
On 25 Apr 2016 16:48, "Carl Baldwin" wrote:
> +1
> On Apr 25, 2016 10:57 AM, "Kyle Mestery" wrote:
>
>> Ihar, Henry and I were talking and we thought Thursday night makes sense
>> for a Neutron social in Austin. If others agree, reply on this thread and
>> we'll find a place.
>>
>> Thanks!
>>
3-31-22.00.log.html#l-231
[3]:
http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-04-14-22.00.log.html#l-153
--
John Schwarz,
Red Hat.
__
OpenStack Development Mailing List (not for usage questions)
U
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
nsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.open
Adding to what Miguel said, I've merged a few months back a patch [1]
which actually fixed the noauth feature in favour of the full-stack
effort (the full-stack patches use neutronclient in noauth mode for easy
access to neutron-server). We'll probably continue to use neutronclient
until some other
+1. I think this is an important feature and I'd be happy to do reviews
when needed - hopefully this can get in by Kilo! :)
On 11/08/2014 12:24 PM, Armando M. wrote:
> Hi Miguel,
>
> Thanks for picking this up. Pull me in and I'd be happy to help!
>
> Cheers,
> Armando
>
> On 7 November 2014 10
produce the result.
[1]
http://eventlet.net/doc/modules/timeout.html#eventlet.timeout.eventlet.timeout.Timeout.Timeout.cancel
[2] https://review.openstack.org/#/c/119001/
[3]
http://stackoverflow.com/questions/2925606/how-to-create-a-cpu-spike-with-a-bash-command
--
John Schwarz,
Software Engineer, Red Hat.
__
On 08/25/2014 10:06 PM, Brandon Logan wrote:
>>
>> 2. Therefor, there should be some configuration to specifically enable
>> either version (not both) in case LBaaS is needed. In this case, the
>> other version is disabled (ie. a REST query for non-active version
>> should return a "not activated
h everyone?
4. If we are going for different API between versions, appropriate
patches also need to be written for lbaas-related scripts and also
Tempest, and their maintainers should probably be notified.
Are there any issues with one of the points raised above? Does anyone
see any other p
19 matches
Mail list logo
