Open Stack

Ildiko, thanks for starting this discussion.

Really, that is quite painful problem for Ceilometer and QA team. As far as
I know, currently there is some kind of tendency of making integration
Tempest tests quicker and less resource consuming - that's quite logical
IMHO. Polling as a way of information collecting from different services
and projects is quite consuming speaking about load on Nova API, etc. -
that's why I completely understand the wish of QA team to get rid of it,
although polling still makes lots work inside Ceilometer, and that's why
integration testing for this feature is really important for me as
Ceilometer contributor - without pollsters testing we have no way to check
its workability.

That's why I'll be really glad if Ildiko's (or whatever other) solution
that will allow polling testing in the gate will be found and accepted.

Problem with described above solution requires some kind of change in what
do we call "environment preparing" for the integration testing - and we
really need QA crew help here. Afair polling deprecation was suggested in
some of the IRC discussions (by only notifications usage), but that's not
the solution that might be just used right now - but we need way of
Ceilometer workability verification right now to continue work on its
improvement.

So any suggestions and comments are welcome here :)

Thanks!
Dina


On Wed, Jul 16, 2014 at 7:06 PM, Ildikó Váncsa <ildiko.vancsa at ericsson.com>
wrote:

>  Hi Folks,
>
>
>
> We’ve faced with some problems during running Ceilometer integration tests
> on the gate. The main issue is that we cannot test the polling mechanism,
> as if we use a small polling interval, like 1 min, then it puts a high
> pressure on Nova API. If we use a longer interval, like 10 mins, then we
> will not be able to execute any tests successfully, because it would run
> too long.
>
>
>
> The idea, to solve this issue,  is to reconfigure Ceilometer, when the
> polling is tested. Which would mean to change the polling interval from the
> default 10 mins to 1 min at the beginning of the test, restart the service
> and when the test is finished, the polling interval should be changed back
> to 10 mins, which will require one more service restart. The downside of
> this idea is, that it needs service restart today. It is on the list of
> plans to support dynamic re-configuration of Ceilometer, which would mean
> the ability to change the polling interval without restarting the service.
>
>
>
> I know that this idea isn’t ideal from the PoV that the system
> configuration is changed during running the tests, but this is an expected
> scenario even in a production environment. We would change a parameter that
> can be changed by a user any time in a way as users do it too. Later on,
> when we can reconfigure the polling interval without restarting the
> service, this approach will be even simpler.
>
>
>
> This idea would make it possible to test the polling mechanism of
> Ceilometer without any radical change in the ordering of test cases or any
> other things that would be strange in integration tests. We couldn’t find
> any better way to solve the issue of the load on the APIs caused by polling.
>
>
>
> What’s your opinion about this scenario? Do you think it could be a viable
> solution to the above described problem?
>
>
>
> Thanks and Best Regards,
>
> Ildiko
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

Best regards,

Dina Belova

Software Engineer

Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140716/bd53b4cd/attachment.html>