onto the
also_messaging. I will add a patch so that it would pick up from the
configuration in oslo_messaging itself.
Thanks & Regards,
Cheran
On 2/14/17, 9:32 PM, "Ken Giusti" wrote:
>On Tue, Feb 14, 2017 at 2:52 PM, Elancheran Subramanian
> wrote:
>> Hello All,
&
Hello All,
This is reg limiting the number of retries for Kafka driver support on Nova and
Neutron.
While trying out the oslo messaging notifications support for Kafka on Nova and
Neutron, the Kafka driver doesn’t support limiting the number of retries for
failed messages. When I checked the co
On 11/30/16, 4:45 PM, "Joshua Harlow" wrote:
>Mehdi Abaakouk wrote:
>> Hi,
>>
>> I think my subject is clear :) , but I will add some facts that can help
>> to the decision:
>> * It uses only deprecated python-kafka API [1] [2]
>> * It's not python3 compatible [3]
>> * We still don't have kafka
Hi Dims,
Thanks for sharing…
Just wanted to check whether there is any development for Nova and Neutron
going on, which we can leverage?
Thanks,
Cheran
On 11/3/16, 12:51 AM, "Davanum Srinivas" wrote:
>Josh,
>
>Kirill Bespalov put together this doc of which components will work
>with sep
n your test plan and what coverage you. Does your test
plan covers V3 Identity tests ? If it does and its failing, you should modify
to make it work for your environment. Fast way to move forward is to exclude
those tests.
-Punal
On Tue, Aug 16, 2016 at 3:40 PM, Elancheran Subramanian
mailto:e
Hello There,
I’m currently playing with using Tempest as our integration tests for our
internal and external clouds, facing some issues with api which are not
supported in our cloud. For ex, listing domains isn’t supported for any user,
due to this V3 Identity tests are failing. So I would like
