Hey Aravind! 'tis a small world after all. The nbr module provides everything in the core runtime sans the specific drivers. You can use the NBLIBDIR env var to load specific driver adapter implementations. Please try it out and let me know if this works for you? I'll try to get this on the new docs site pretty soon.

I know this is late, but I'm going to answer it anyway.

You can do that. It is built into the scripting layer. Essentially, any workload you run with NB can be captured in its native scripting form simply by calling --show-script. This dumps out the scenario control script which is created on users' behalf for trivial cases.

If you modify the activities.<alias>.rate parameter with a string matching what you would use with an activity parameter, it will apply the change immediately and rates will adapt. The scripting docs cover some of this.

The recipe for this is pretty straightforward:

1. start your activity instead of running it.
2. While it is running asynchronously to the main control script, just loop over a time delay and setting the variable above as you need.
3. Watch it go!

My apologies for not catching this when you asked. It's been a very busy year!