On Thu, Jan 9, 2014 at 8:49 AM, Pádraig Brady pbrady@redhat.com wrote:
On 01/09/2014 12:56 PM, Nux! wrote:
On 09.01.2014 12:08, Josh Boyer wrote:
On Wed, Jan 8, 2014 at 8:24 PM, Lars Kellogg-Stedman lars@redhat.com wrote:
On Wed, Jan 08, 2014 at 08:07:15PM -0500, Josh Boyer wrote:
What need for a different kernel has come up with the RDO/OpenStack
For RDO/OpenStack we needed network namespace support (to support Neutron) that wasn't available in the stock RHEL/CentOS kernel.
Was that solved with some backporting to the RHEL/CentOS kernel, or did you wind up using an entirely newer kernel version?
Also GRE and the newer VXLAN support were added. These were significant additions best managed within a full kernel release. Note since CentOS 6.5 these have been incorporated into the main kernel, but the point still remains that we can benefit from a separate kernel on occasion.
OK, but it's still a kernel based on the RHEL kernel, just with the changes/additions backported to it. It isn't a bump to e.g. the Linux 3.10 stable release or something. Correct?
Separate kernels and iproute were/are necessary, they are provided in this repo http://repos.fedorapeople.org/repos/openstack/openstack-havana/epel-6/
AFAIK netns is still unsupported in EL 6.5, iproute can't handle netns for example.
The netns backport is not complete due to kernel ABI constraints. With the older RDO kernel and with the newer CentOS 6.5 kernel you can specify the netns of a link but you can't use 'ip netns'.
Right. I wonder how much kABI is going to play into CentOS variants. Frankly, I hope the answer is "not much".
The above linked repo is also a good place to browse candidate packages for the cloud sig. Given OpenStack is implemented in python, there are some new and/or backwards incompatible python libraries there. But also there are more general packages like the above discussed kernel for 6.4 based systems and openvswitch packages etc.
Good to know, thanks.
josh