Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

avoid kmod-openvswitch installation for non-2.6 kver #924

wants to merge 1 commit into from

Conversation

xdel
Copy link
Contributor

@xdel xdel commented Dec 9, 2013

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

@mirantis-jenkins
Copy link

Merged build triggered.

1 similar comment
@mirantis-jenkins
Copy link

Merged build triggered.

@mirantis-jenkins
Copy link

Merged build started.

@mirantis-jenkins
Copy link

Merged build finished.

@mirantis-jenkins
Copy link

👎 Test FAILed.
Refer to this link for build results: http://fuel-jenkins.mirantis.com/job/fuel_pullrequest_systest/272/

@xarses
Copy link
Contributor

xarses commented Dec 9, 2013

How does this depercrate vlan splinters?

@xdel
Copy link
Contributor Author

xdel commented Dec 10, 2013

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.

@mirantis-jenkins
Copy link

Merged build started.

@mirantis-jenkins
Copy link

Merged build finished.

@mirantis-jenkins
Copy link

👍 Test PASSed.
Refer to this link for build results: http://fuel-jenkins.mirantis.com/job/fuel_syntax_check/721/

@xarses
Copy link
Contributor

xarses commented Dec 10, 2013

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

@xdel
Copy link
Contributor Author

xdel commented Dec 10, 2013

It should not be default selection but only for models having unbeatable issue with connectivity in VLAN isolation mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants