Hi,
Steps 3 and 4 are not necessary (but at the same time they do not harm),
because configuration in step 2 is what really used to get packages for the
image.
Anyway, glad to see your issue resolved.
A bit more extended explanation on why steps 3 and 4 are not mandatory:
1. During Fuel master no
Hi Evgeniy,
I built a repository and added my DKMS deb package into the repository,
then added repository URL and package name into:
1. /etc/fuel-bootstrap-cli/fuel_bootstrap_cli.yaml
2. Fuel UI > Settings > General
3. /usr/lib/python2.7/site-packages/nailgun/fixtures/openstack.yaml
4. /usr/share/
You have several options:
1. Build new repository and configure your environment to use it (pay
attention to repositories priority).
2. Add package to existing repository, and rebuild the repo (to update
metadata about the packages).
1st option is more preferable, it would simplify for you further
Hi Evgeniy, thanks for the reply first.
According from your options, I have a idea about first option
Since I already built a driver as DKMS module, I may try to put package
into a repository that inside a Fuel Master node. And add package name into
the installation list so that DKMS module will
Hi,
Bootstrap image is used only when node is in discovery state (before
provisioning is done), when you send nodes for provisioning, Fuel builds an
image using repository from environment configuration, after the image is
built, it reuses it for future deployments you can find details in
document
Hi everyone,
I'm using Fuel 9.1 to deploy OpenStack, but I found that the kernel still
too old to support Intel i219-LM NIC card.
So I'm followed the instruction from OpenStack Documents and built the
bootstrap kernel with latest e1000e driver. Then tested and it successfully
catch i219-LM inform
