Intel Xeon D 10G requires newer ixgbe version

In the current implementation dkms modules are placed in the local repository or MOS repositories.
Take a look at the i40e-dkms module as an example.
This module included into list of packages required for building bootstrap and IBP images.
(Please see for bootstrap the config file /etc/fuel-bootstrap-cli/fuel_bootstrap_cli.yaml )
If you have prepared dkms module build as a deb package you can add it to a repository, add the repositories and include to the list of packages as it done for i40e-dkms.
PS
We can try building the ixgbe-dkms like it has been done for i40e-dkms.

PS2
It backward tendency (from Intel), that kernel has quite outdated kernel modules shipped with it, but the last stable drivers are placed on sourceforge.

I'm able to get it done for the bootstrap by adding it to a repository and update the fuel_bootstrap_cli.yaml however i can't get it to work for the provisioning image.

How do I tell MOS that not only it should add the repository (which i can via the configuration) but also actually load the package ixgbe-dkms upon provisioning.

Best would be if ixgbe-dkms would be added to the MOS repository just like i40e-dkms was.

Hello Eric,

To get the ixgbe-dkms included into image you should add it to the package
list.
The script
/usr/lib/python2.6/site-packages/fuel_agent/drivers/nailgun.py
build image for provisioning Ubuntu and it contains the list of packages.
Please run the command to locate in the code
grep
i40e-dkms /usr/lib/python2.6/site-packages/fuel_agent/drivers/nailgun.py

You can merely add your ixgbe-dkms package to the list of the python
script.

To add the ixgbe-dkms package to the Ubuntu repositories you need reprepro
on CentOS, because the Fuel master node based on CentOS

The Ubuntu repository is placed at the path
/var/www/nailgun/ubuntu/x86_64/

You should create conf dir inside the repository and add incoming file:
mkdir conf
cd conf

And put the lines like this into the file "incoming"
---
Name:
Default:
IncomingDir: ./
TempDir: /tmp/
---
Into the file "conf"
--
verbose
basedir .
--
Into the file "distributions"
--
Origin: Mirantis
Label: Mirantis MOS
Suite: stable
Codename: trusty
Architectures: amd64
Components: main
---

Please see the reprepro manual for details

You should run the command
reprepro includedeb ixgbe-dkms

what will add your ixgbe-dkms deb package to the repository.

PS
As I know Fedora has reprepro rpm what could be used for managing debian
repositories.

Regards,

Albert Syriy,

Software Engineer,
Mirantis

On Tue, Sep 13, 2016 at 12:03 AM, Eric van Vliet <
<email address hidden>> wrote:

> I'm able to get it done for the bootstrap by adding it to a repository
> and update the fuel_bootstrap_cli.yaml however i can't get it to work
> for the provisioning image.
>
> How do I tell MOS that not only it should add the repository (which i
> can via the configuration) but also actually load the package ixgbe-dkms
> upon provisioning.
>
> Best would be if ixgbe-dkms would be added to the MOS repository just
> like i40e-dkms was.
>
> --
> You received this bug notification because you are a member of MOS
> Linux, which is a bug assignee.
> https://bugs.launchpad.net/bugs/1621218
>
> Title:
> Intel Xeon D 10G requires newer ixgbe version
>
> Status in Mirantis OpenStack:
> Confirmed
> Status in Mirantis OpenStack 8.0.x series:
> Confirmed
> Status in Mirantis OpenStack 9.x series:
> Confirmed
>
> Bug description:
> Detailed bug description:
> The Intel Xeon D SoC has 2 onboard 10G ports, they require ixgbe module
> 4.2.5 or upwards.
> Ubuntu 14.04 trusty comes with a lower version, so you have to upgrade
> the driver.
>
> Steps to reproduce:
> Install Ubuntu 14.04 on a Xeon D platform and check the loaded network
> ports
>
> Expected results:
> Recognize the 2x 10G ports that are on the Xeon D SoC
>
> Actual result:
> The 2x 10G ports aren't detected
>
> Workaround:
> I've created a dkms with ixgbe 4.2.5 however you have to manually update
> the ubuntu installation, which means let it fail and download&install the
> deb file on each server.
>
> Impact:
> Xeon D, a processor family that targets microservers isn't compatible
> with Mirantis Openstack running Ubuntu 14.04
>
> What is the best cause of action for this?
> Create a plugin, will this plugin be installed before Openstack
> depl...

centos doesn't offer reprepro i've managed to get it all done..

however alternatively couldn't i just change the trusty kernel packages to the xenial kernel packages in that file: /usr/lib/python2.6/site-packages/fuel_agent/drivers/nailgun.py

        "linux-headers-generic-lts-xenial",
        "linux-image-generic-lts-xenial",

this way we are still using at LTS kernel that is supported by Ubuntu plus we are far more up to date with all security patches plus drivers.

Hello Evid,

Yes, exactly.
You can switch to the new lts kernel (now 4.4) by changing the "trusty" to "xenial".
It works.

In MOS 7.0 you should edit the list of installed packages in the file /usr/lib/python2.6/site-packages/fuel_agent/drivers/nailgun.py placed in mcollective docker container.

In newer MOS since 8.0 you can edit the list of packages through Fuel Web using Tab "Settings" (at the bottom of the page where repositories are).

Here the steps for MOS 7.x:

$ dockerctl shell mcollective
$ vi /usr/lib/python2.6/site-packages/fuel_agent/drivers/nailgun.py
 (Edit list of packages and change trusty on xenial in the linux-*-generic-lts-trusty packages).
$ exit

Restart mcollective container to apply changes in the file.

Delete base images in the /var/www/nailgun/targetimages/ for required cluster_id.

For example for cluster 1 it could be:
env_1_ubuntu_1404_amd64-boot.img.gz
env_1_ubuntu_1404_amd64.img.gz

And redeploy the cluster. The new base image containing new lts kernel will be build and deployed.

For Fuel newer versions (8.x and 9.x) you just edit list of packages on the WEB page, delete the base images and redeploy cluster.

The new package has been built
Here the commit
https://review.fuel-infra.org/#/c/26443/2

Here you can download the package from the link
http://perestroika-repo-tst.infra.mirantis.net/mos-repos/xenial/master/pool/main/i/ixgbe-dkms/

Hi,

Couple things.. First of all thanks for the build, I can however not download the package..

1. Should I update any repo file like package.gz..?
2. Will you build one for Trusty as for Xenial a version of ixgbe is already included that supports the xeon d 10g interfaces

Eric

Hello Eric,

See my comments:

1. Should I update any repo file like package.gz..?
Actually I didn't understand your question.
You can create (or update Package.gz) manually.

2. Will you build one for Trusty as for Xenial a version of ixgbe is already included that supports the xeon d 10g interfaces

I have build the package for Xenial. You can download it from the repository
http://mirror.fuel-infra.org/mos-repos/xenial/master/ main

Actually the package is the same for xenial and trusty, but since we have two separate project on trusty and xenial, we have the file for both.

PS
I tested and ixgbe-dkms successfully built with both current kernels versions 3.13.95 and 4.4.6

PS 2:
The direct link to the package is
http://mirror.fuel-infra.org/mos-repos/xenial/master/pool/main/i/ixgbe-dkms/ixgbe-dkms_4.4.6-1~u16.04%2bmos1_all.deb

Hello Albert,

Ok so i've added the ixgbe-dkms you provided to the mos8.0 repo on my fuel master, i'm able to build a new bootstrap image that includes the ixgbe-dkms without any issues.

Now I am provisioning and it doesnt include the ixgbe-dkms upon installation, i've added the ixgbe-dkms to the /usr/lib/python2.7/site-packages/fuel_agent/drivers/nailgun.py however it's not installed during provisioning process.

you said something about being able to add the packages on the web interface however i can't do that. I can add repo's however not define which packages are installed.

Eric

Hello Eric,

Please pay attantion to two things:
1. You should definitely delete (or rename) previously built base images in
the folder /var/www/nailgun/targetimages/
In my case the images are called:
env_1_ubuntu_1404_amd64-boot.img.gz
env_1_ubuntu_1404_amd64.img.gz
( where "1" in the name is ID of the deployed cluster. You should have
something similar to that in your targetimage folder).

Please keep untouched the yaml file!

If you not delete the base images, they will not be re-build (prior the
provisioning phase) and the (old) image with the old kernel will be
installed.
Please check time of the images (files) to be sure, that they were rebuilt.

2. You should modify list of packages in nailgun.py. And change "trusty" to
"xenial".
Unfortunately I don't have a mos8.0 deployed close at hand.
I recall that on <Tab> "settings" at the bottom of the page should be a
list of packages which to be installed into base image.
And you should modify linux-image-lts-trusty (to *-xenial)

If I am not correct and there is not list of packages in the widow in
mos-8.0, than modify the nailgun.py file.

And press deploy button to install new image with new kernel.

You also could run on the deployed nodes a few CLI commands:
1) Install new kernel
apt-get -q update && apt-get install -qy linux-image-generic-lts-xenial
linux-headers-generic-lts-xenial
2) Rebuild dkms kernel modules (if any were missed during the kernel
upgrade)
dkms status
dkms build -m <module>/<version> -k <new kernel version>

3) Modify mount option xfs (for new kernel 4.4)

if [ -f /etc/ceph/ceph.conf]; then
 sed -i 's|^osd_mount_options_xfs = .*|osd_mount_options_xfs =
rw,relatime,inode64,logbsize=256k,allocsize=4M|g' /etc/ceph/ceph.conf

fi
Regards,

Albert Syriy,

Software Engineer,
Mirantis

On Tue, Sep 20, 2016 at 8:33 PM, Eric van Vliet <<email address hidden>
> wrote:

> Hello Albert,
>
> Ok so i've added the ixgbe-dkms you provided to the mos8.0 repo on my
> fuel master, i'm able to build a new bootstrap image that includes the
> ixgbe-dkms without any issues.
>
> Now I am provisioning and it doesnt include the ixgbe-dkms upon
> installation, i've added the ixgbe-dkms to the /usr/lib/python2.7/site-
> packages/fuel_agent/drivers/nailgun.py however it's not installed during
> provisioning process.
>
> you said something about being able to add the packages on the web
> interface however i can't do that. I can add repo's however not define
> which packages are installed.
>
> Eric
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1621218
>
> Title:
> Intel Xeon D 10G requires newer ixgbe version
>
> Status in Mirantis OpenStack:
> In Progress
> Status in Mirantis OpenStack 8.0.x series:
> In Progress
> Status in Mirantis OpenStack 9.x series:
> In Progress
>
> Bug description:
> Detailed bug description:
> The Intel Xeon D SoC has 2 onboard 10G ports, they require ixgbe module
> 4.2.5 or upwards.
> Ubuntu 14.04 trusty comes with a lower version, so you have to upgrade
> the driver.
>
> Steps to reproduce:
> Install Ubuntu 14.04 on a Xeon D platform and check the loaded network
> ports
>
> Expected ...

Hi Albert,

so the strange thing is that for the env_1 i had both i40e-dkms and ixgbe-dkms nailgun.py however in the env_1 yaml file only i40e-dkms is listed as package.

to test the effect of the nailgun.py file changes i removed i40e-dkms and attempted to build a 2nd environment. now the env_2 yaml file still contains i40e-dkms and still no ixgbe-dkms.

the changes in the nailgun.py package list seem to have no effect on the packages that are included in the provisioning image.

Any clue how to do this in MOS 8

I'm going to install MOS9 Fuel master on another blade now to see if i can get the package included via the web client as you said.

Eric

Hello,

There are differences in mos-7.x 8.x and 9.x
Unfortunately I don't have mos-8.0 lab deployed now.

Could be the yaml file contains list of packages using for building base
image.
I don't know exactly.
But if you change (add/delete/edit) list through the WEB it works, at least
I checked it in MOS-9.0

Regards,

Albert Syriy,

Software Engineer,
Mirantis

On Wed, Sep 21, 2016 at 8:22 AM, Eric van Vliet <<email address hidden>
> wrote:

> Hi Albert,
>
> so the strange thing is that for the env_1 i had both i40e-dkms and
> ixgbe-dkms nailgun.py however in the env_1 yaml file only i40e-dkms is
> listed as package.
>
> to test the effect of the nailgun.py file changes i removed i40e-dkms
> and attempted to build a 2nd environment. now the env_2 yaml file still
> contains i40e-dkms and still no ixgbe-dkms.
>
> the changes in the nailgun.py package list seem to have no effect on the
> packages that are included in the provisioning image.
>
> Any clue how to do this in MOS 8
>
> I'm going to install MOS9 Fuel master on another blade now to see if i
> can get the package included via the web client as you said.
>
> Eric
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1621218
>
> Title:
> Intel Xeon D 10G requires newer ixgbe version
>
> Status in Mirantis OpenStack:
> In Progress
> Status in Mirantis OpenStack 8.0.x series:
> In Progress
> Status in Mirantis OpenStack 9.x series:
> In Progress
>
> Bug description:
> Detailed bug description:
> The Intel Xeon D SoC has 2 onboard 10G ports, they require ixgbe module
> 4.2.5 or upwards.
> Ubuntu 14.04 trusty comes with a lower version, so you have to upgrade
> the driver.
>
> Steps to reproduce:
> Install Ubuntu 14.04 on a Xeon D platform and check the loaded network
> ports
>
> Expected results:
> Recognize the 2x 10G ports that are on the Xeon D SoC
>
> Actual result:
> The 2x 10G ports aren't detected
>
> Workaround:
> I've created a dkms with ixgbe 4.2.5 however you have to manually update
> the ubuntu installation, which means let it fail and download&install the
> deb file on each server.
>
> Impact:
> Xeon D, a processor family that targets microservers isn't compatible
> with Mirantis Openstack running Ubuntu 14.04
>
> What is the best cause of action for this?
> Create a plugin, will this plugin be installed before Openstack
> deployment starts?
> Create a local repository from which the dkms is loaded, how do i force
> the ixgbe to be reloaded because the ubuntu already comes with ixgbe module.
> Add the ixgbe that comes with Ubuntu 16.04 to the standard mos8/9 repo?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mos/+bug/1621218/+subscriptions
>

hey,
so some sort of success with MOS9, i've been able to get the blades up and running with ubuntu 14.04 and include the ixgbe-dkms driver automatically.

However now it fails all 3 controllers with the following error

2016-09-21 10:24:01 ERR (/Stage[main]/Cluster::Vrouter_ocf/Service[p_vrouter]/ensure) change from stopped to running failed: Execution timeout after 1800 seconds!

Now because it's vrouter, thus network related, i'm concerned this is caused by the fax we load a later version ixgbe version? Anyway you said you had success by fully deploying MOS9?

Eric

Yes, I did deploy MOS 9
Please contact to the support team for help.

Won't Fix for 8.0.x series as we don't add new features (including new hardware support) to maintenance updates.

https://review.fuel-infra.org/#/c/26806/

The ixgbe-dkms package has been committed into 9.1

I close this bug according comment:

>Ok so i've added the ixgbe-dkms you provided to the mos8.0 repo on my fuel master, i'm able to >build a new bootstrap image that includes the ixgbe-dkms without any issues.

Just for anyone who want to patch Mirantis 9.0 with the ixgbe dkms here is what i've done

Ubuntu 14.04 Trusty kernel with upgraded ixgbe kernel module
1. Create a folder in the ubuntu repository of MOS9
-- mkdir /var/www/nailgun/ubuntu/x86_64/pool/main/i/ixgbe-dkms

2. Download the ixgbe-dkms deb file into the created folder
-- wget http://mirror.fuel-infra.org/mos-repos/xenial/master/pool/main/i/ixgbe-dkms/ixgbe-dkms_4.4.6-1~u16.04%2bmos1_all.deb

3. Add the ixgbe-dkms information to the Package file
-- wget http://mirror.fuel-infra.org/mos-repos/xenial/master/dists/mos-master/main/binary-amd64/Packages
-- find ixgbe-dkms in that file and copy the whole section into your local Packages file in /var/www/nailgun/ubuntu/x86_64/dists/mos9.0/main/binary-amd64/Packages
   Package: ixgbe-dkms
   Version: 4.4.6-1~u16.04+mos1
   Architecture: all
   Maintainer: Mirantis Openstack Linux Team <email address hidden>
   Installed-Size: 1860
   Depends: dkms (>= 1.95)
   Priority: optional
   Section: misc
   Filename: pool/main/i/ixgbe-dkms/ixgbe-dkms_4.4.6-1~u16.04+mos1_all.deb
   Size: 319466
   SHA256: 2ed85c625065918e5bdf5a5fec151f122cc766f7548e3af1222c02e305aa333c
   SHA1: 7b12e65c71e690bbed8a82bd2e4323e54dcaad89
   MD5sum: c5482590cd6ae879d9704240cc22cac6
   Description: ixgbe driver in DKMS format.

4. Delete the Package.gz and Package.bz2 and repackage the new Package file
-- gzip -c Package > Package.gz
-- bzip2 -c Package > Package.gz

5. Replace the MD5SUM, SHA1 and SHA256 in the /var/www/nailgun/ubuntu/x86_64/dists/mos9/Release file
-- cd /var/www/nailgun/ubuntu/x86_64/dists/mos9/
-- md5sum main/binary-amd64/Package*
Example of my output, please do not use this but use your own output
   bdb684f6c9ee48697e1ee4a9aabe5378 main/binary-amd64/Packages
   8ffd5b785641aaf7fc379e338ae06459 main/binary-amd64/Packages.bz2
   7743dd018ae1c8973bcc53fdeb661df7 main/binary-amd64/Packages.gz

-- sha1sum main/binary-amd64/Package*
Example of my output, please do not use this but use your own output
   3e05409283082a8b12bbf9181de7b09d7c2b8d93 main/binary-amd64/Packages
   c57de1d88d026e4e7c0e847f615b87caeb176f04 main/binary-amd64/Packages.bz2
   cd6d4176d0b2989eb6c470129017e4e943bf43d0 main/binary-amd64/Packages.gz

-- sha256sum main/binary-amd64/Package*
Example of my output, please do not use this but use your own output
   5afefb41710fce06c9cd92be8f4592195f20f4520d73b655d1912a13447896b3 main/binary-amd64/Packages
   819341558eb803dae38114253e65254458e2e1e7db4dce63691693ef5425b6f6 main/binary-amd64/Packages.bz2
   e45c394444bc187351018424a2c4da90e8f978fe13ada782c9833df959d0203a main/binary-amd64/Packages.gz

-- edit /var/www/nailgun/ubuntu/x86_64/dists/mos9/Release
   Origin: Mirantis
   Label: mos9.0
   Suite: mos9.0
   Codename: mos9.0
   Date: Thu, 16 Jun 2016 18:25:43 UTC
   Architectures: amd64
   Components: main restricted
   Description: Mirantis OpenStack mirror
   MD5Sum:
    bdb684f6c9ee48697e1ee4a9aabe5378 1586679 main/binary-amd64/Packages
    7743dd018ae1c8973bcc53fdeb661df7 381975 main/binary-amd64/Packages.gz
    8ffd5b785641aaf7fc379e338ae06459 278108 main/binary-amd64/Packages.bz2
    dbf57d312f8a27eb0e6d07a701a68104 122 main/...

Hello Eric,

Since MOS 9.1 release the package will have appeared in the Ubuntu
repository.
But you should manually add it to bootstrap package list and base image
package list to have it in bootstrap and base image correspondingly.

Regards,

Albert Syriy,

Software Engineer,
Mirantis

On Wed, Oct 5, 2016 at 10:59 AM, Eric van Vliet <<email address hidden>
> wrote:

> Just for anyone who want to patch Mirantis 9.0 with the ixgbe dkms here
> is what i've done
>
> Ubuntu 14.04 Trusty kernel with upgraded ixgbe kernel module
> 1. Create a folder in the ubuntu repository of MOS9
> -- mkdir /var/www/nailgun/ubuntu/x86_64/pool/main/i/ixgbe-dkms
>
> 2. Download the ixgbe-dkms deb file into the created folder
> -- wget http://mirror.fuel-infra.org/mos-repos/xenial/master/pool/
> main/i/ixgbe-dkms/ixgbe-dkms_4.4.6-1~u16.04%2bmos1_all.deb
>
> 3. Add the ixgbe-dkms information to the Package file
> -- wget http://mirror.fuel-infra.org/mos-repos/xenial/master/dists/
> mos-master/main/binary-amd64/Packages
> -- find ixgbe-dkms in that file and copy the whole section into your local
> Packages file in /var/www/nailgun/ubuntu/x86_64/dists/mos9.0/main/binary-
> amd64/Packages
> Package: ixgbe-dkms
> Version: 4.4.6-1~u16.04+mos1
> Architecture: all
> Maintainer: Mirantis Openstack Linux Team <email address hidden>
> Installed-Size: 1860
> Depends: dkms (>= 1.95)
> Priority: optional
> Section: misc
> Filename: pool/main/i/ixgbe-dkms/ixgbe-dkms_4.4.6-1~u16.04+mos1_all.deb
> Size: 319466
> SHA256: 2ed85c625065918e5bdf5a5fec151f122cc766f7548e3af1222c02e305aa
> 333c
> SHA1: 7b12e65c71e690bbed8a82bd2e4323e54dcaad89
> MD5sum: c5482590cd6ae879d9704240cc22cac6
> Description: ixgbe driver in DKMS format.
>
> 4. Delete the Package.gz and Package.bz2 and repackage the new Package file
> -- gzip -c Package > Package.gz
> -- bzip2 -c Package > Package.gz
>
> 5. Replace the MD5SUM, SHA1 and SHA256 in the /var/www/nailgun/ubuntu/x86_64/dists/mos9/Release
> file
> -- cd /var/www/nailgun/ubuntu/x86_64/dists/mos9/
> -- md5sum main/binary-amd64/Package*
> Example of my output, please do not use this but use your own output
> bdb684f6c9ee48697e1ee4a9aabe5378 main/binary-amd64/Packages
> 8ffd5b785641aaf7fc379e338ae06459 main/binary-amd64/Packages.bz2
> 7743dd018ae1c8973bcc53fdeb661df7 main/binary-amd64/Packages.gz
>
> -- sha1sum main/binary-amd64/Package*
> Example of my output, please do not use this but use your own output
> 3e05409283082a8b12bbf9181de7b09d7c2b8d93 main/binary-amd64/Packages
> c57de1d88d026e4e7c0e847f615b87caeb176f04
> main/binary-amd64/Packages.bz2
> cd6d4176d0b2989eb6c470129017e4e943bf43d0 main/binary-amd64/Packages.gz
>
> -- sha256sum main/binary-amd64/Package*
> Example of my output, please do not use this but use your own output
> 5afefb41710fce06c9cd92be8f4592195f20f4520d73b655d1912a13447896b3
> main/binary-amd64/Packages
> 819341558eb803dae38114253e65254458e2e1e7db4dce63691693ef5425b6f6
> main/binary-amd64/Packages.bz2
> e45c394444bc187351018424a2c4da90e8f978fe13ada782c9833df959d0203a
> main/binary-amd64/Packages.gz
>
> -- edit /var/www/nailgun/ubuntu/x86_64/dists/mos9/Rele...

Hi,

What is the release schedule for 9.1?

Eric

Hello,

According the schedule
https://wiki.openstack.org/wiki/Fuel/Release_Schedule

the general available (GA) ISO should be issued on 19 October 2016.

Regards,

Albert Syriy,

Software Engineer,
Mirantis

On Wed, Oct 5, 2016 at 12:54 PM, Eric van Vliet <<email address hidden>
> wrote:

> Hi,
>
> What is the release schedule for 9.1?
>
> Eric
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1621218
>
> Title:
> Intel Xeon D 10G requires newer ixgbe version
>
> Status in Mirantis OpenStack:
> Fix Released
> Status in Mirantis OpenStack 8.0.x series:
> Won't Fix
> Status in Mirantis OpenStack 9.x series:
> Fix Released
>
> Bug description:
> Detailed bug description:
> The Intel Xeon D SoC has 2 onboard 10G ports, they require ixgbe module
> 4.2.5 or upwards.
> Ubuntu 14.04 trusty comes with a lower version, so you have to upgrade
> the driver.
>
> Steps to reproduce:
> Install Ubuntu 14.04 on a Xeon D platform and check the loaded network
> ports
>
> Expected results:
> Recognize the 2x 10G ports that are on the Xeon D SoC
>
> Actual result:
> The 2x 10G ports aren't detected
>
> Workaround:
> I've created a dkms with ixgbe 4.2.5 however you have to manually update
> the ubuntu installation, which means let it fail and download&install the
> deb file on each server.
>
> Impact:
> Xeon D, a processor family that targets microservers isn't compatible
> with Mirantis Openstack running Ubuntu 14.04
>
> What is the best cause of action for this?
> Create a plugin, will this plugin be installed before Openstack
> deployment starts?
> Create a local repository from which the dkms is loaded, how do i force
> the ixgbe to be reloaded because the ubuntu already comes with ixgbe module.
> Add the ixgbe that comes with Ubuntu 16.04 to the standard mos8/9 repo?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mos/+bug/1621218/+subscriptions
>

I freshly installed Fuel master using the 9.0 ISO, updated it to 9.1 however i can't see the ixgbe-dkms file in the ubuntu pool.. Have you solved this bug differently than previously mentioned?

"Eric van Vliet (eric-vanvliet) wrote on 2016-11-01:
I freshly installed Fuel master using the 9.0 ISO, updated it to 9.1 however i can't see the ixgbe-dkms file in the ubuntu pool.. Have you solved this bug differently than previously mentioned?"

I can confirm the exact same issue. Couple of days ago freshly installed MOS 9.0 -> updated to 9.1. Slave node contains Ubuntu 14.0.5 LTS and no 10GbE.

Platforms:
- Supermicro X10SDV-TLN4F (Controller nodes)
- Supermicro X10SDV-8C-TLN4F (Compute nodes)
- ASRock Rack EPC612D4U-2T8R (Storage nodes)

Questions
1. How to check/validate the correct driver set within the bootstrap versions?
2. Has anyone created a new Ubuntu bootstrap image with the above mentioned Debian binary file?

Hey Remko,

Basically the ixgbe-dkms is included in both 9.0 and 9.1 pool
http://mirror.fuel-infra.org/mos-repos/ubuntu/9.0/pool/main/i/ixgbe-dkms/
http://mirror.fuel-infra.org/mos-repos/ubuntu/9.1/pool/main/i/ixgbe-dkms/

So after you install MOS 9.0 from the iso image simply do "fuel-createmirror -M" to synchronize your MOS repo with the latest one from the mos-repo.

Afterwards build a new bootstrap image:
fuel-bootstrap --debug build --label 'with_ixgbe-dkms' --package ixgbe-dkms --activate

Finally when you build your openstack environment under settings you need to add the ixgbe-dkms to the list of packages before building it.

Eric (if any questions duke_ehv is me on skype)

@Eric: Thank you very much (In Dutch: Ontzettend bedankt)!! It solved my 10GbE issues.