Hi Ajay, I am not sure why you are looking that part at all. everything in openstack/common/* is oslo-incubator code. Actually that method is not used in Rally yet, except Rally as a Service part that doesn't work yet. As a scenario developer I think you should be able to find everything here: https://github.com/stackforge/rally/tree/master/rally/benchmark So I really don't the case when you need to pass something to periodic task.. It's not that "task" Best regards, Boris Pavlovic On Fri, Nov 21, 2014 at 3:36 AM, Ajay Kalambur (akalambu) < akalambu at cisco.com> wrote: > Hi > I have a question on > /rally/openstack/common/periodic_task.py > > It looks like if I have a method decorated with @periodic_task my method > would get scheduled in separate process every N seconds > Now let us say we have a scenario and this periodic_task how does it work > when concurrency=2 for instance > > Is the periodic task also scheduled in 2 separate process. I actually > want only one periodic task process irrespective of concurrency count in > scenario > Also as a scenario developer how can I pass arguments into the periodic > task > > > Ajay > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141121/bfb0874d/attachment.html>