-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop using a forked Rally #63
Comments
@mestery Thanks for tracking this. The ongoing work of unbounding from openstack in Rally seems not yet completed. I saw this spec [1] merged, but some related works has been pending for a long time, e.g. [2], [3]. [1] https://review.openstack.org/#/c/244353/17 |
unbound rally from openstack [1] [1] https://github.com/openstack/rally/blob/master/doc/specs/in-progress/deployment_type.rst |
As I know, the work of unbound rally from openstack is still going on. If we want to stop to use https://github.com/l8huang/rally.git as early as possible, we may make changes on ovn-scale-test to make it depending on upstream rally. |
@l8huang Does that mean we need to rebase our change against the latest rally codebase? Thanks. |
We'd better rebase to a release, e.g 5.0, because the master stream may not stable. Any suggests? |
@l8huang not yet; it seems the only way to get rid of this issue. Thanks. |
Our local Rally changes should be pushed upstream and we should not rely on a fork [1].
[1] http://ovn-scale-test.readthedocs.io/en/latest/install.html
The text was updated successfully, but these errors were encountered: