2dd7fe17d1
So, when you pip install openstacksdk you all install some of the workflows for the openstack * commands, this means when you create a virtualenv with no system site packages commands like openstack node import don't work the same way and worse we're not testing the same stuff we ship. on the other hand the system version of openstacksdk often isn't sutible for the api call functionality yoda uses, so we need to be sure the command line functionality of yoda goes through the system opesntack client path whereas the api monitoring functions go through openstack sdk, to make this even more complex the subprocess function of python insists on not behaving like a normal shell. This prefixes all bommands with env -i bash -c "command" which runs bash with no way to inherit vars (like the python venv) from Browbeat itself which can then safely rely on the openstacksdk in it's venv Change-Id: I4da896ea793f44ecff8fa0caa82255259447facc
Browbeat
Browbeat is a performance tuning and analysis tool for OpenStack. Browbeat is free, Open Source software.
- Analyze and tune your Cloud for optimal performance.
- Create Rally workloads for performance and scale testing.
- Automate deployment of common data analysis tools.
Documentation
Browbeat documentation is available at http://browbeat.readthedocs.io/
Resources
- Blog
- Code Review
- Git Web
- IRC -- #openstack-browbeat (irc.freenode.net)