-
Notifications
You must be signed in to change notification settings - Fork 44
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
avoid kmod-openvswitch installation for non-2.6 kver #924
base: master
Are you sure you want to change the base?
Conversation
Merged build triggered. |
1 similar comment
Merged build triggered. |
Merged build started. |
Merged build finished. |
👎 Test FAILed. |
How does this depercrate vlan splinters? |
This exact commit does not deprecate them but usage of 3.10+ kernel does - it will be replacement for current splinters-inavoidable cases. We will have no overhead for any imaginable vlan ranges and slightly broader HCL paying by kABI breakage. Old 2.6.32 will remain as a default selection of course. |
Merged build started. |
Merged build finished. |
👍 Test PASSed. |
At least one user has indicated that the 3.10 kernel causes panic's on their hardware (Slightly Older HP Blade) Moving to fedora kernel Isn't a good option for everyone. This also indicates that further hardware testing must be done prior to accepting the new kernel |
It should not be default selection but only for models having unbeatable issue with connectivity in VLAN isolation mode. |
Proposed-for: https://blueprints.launchpad.net/fuel/+spec/cisco-ucs-imp
Milestone: 4.1
Deprecates: VLAN splinters usage
Depends-on: bound removal between kmod-openvswitch and openvswitch packages, nailgun kernel selection passthrough