Open Stack

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/fuel-openstack-metadata/openstack.yaml

(For position 3 and 4, I wish it can install driver during provisioning. I
tried not to do 3 and 4 but seems like it didn't install package after
provision.)

After that, rebuild the new bootstrap and environment images, then driver
successfully updated.

Thanks for the advice, really appreciate!

Eddie.

2017-02-11 6:25 GMT+08:00 Evgeniy L <eli at mirantis.com>:

> 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 upgrades.
>
> Thanks,
>
> On Tue, Feb 7, 2017 at 5:35 PM, Eddie Yen <missile0407 at gmail.com> wrote:
>
>> 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 install during bootstrap
>> image or environment image build.
>>
>> Is that feasible?
>>
>> Thanks,
>> Eddie.
>>
>> 2017-02-08 2:18 GMT+08:00 Evgeniy L <eli at mirantis.com>:
>>
>>> 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
>>> documentation, for example here [1] "Image building" section.
>>> You have multiple options:
>>> 1. Make sure that new kernel is available in configured repository,
>>> remove image from "/var/www/nailgun/targetimages" run deployment of new
>>> nodes, which would trigger image rebuild.
>>> 2. More safe option would be to rebuild image in place
>>> "/var/www/nailgun/targetimages", in this case don't forget to update
>>> checksums in "env_1_ubuntu_1404_amd64.yaml" file.
>>>
>>> Thanks,
>>>
>>> [1] https://docs.mirantis.com/openstack/fuel/fuel-9.1/refere
>>> nce-architecture/single/index.html
>>>
>>> On Sun, Feb 5, 2017 at 11:42 PM, Eddie Yen <missile0407 at gmail.com>
>>> wrote:
>>>
>>>> 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 information in Fuel UI and bootstrap node.
>>>>
>>>> But after these, I thought a one problem. Even I successfully modify
>>>> bootstrap kernel, it will got no changes and may cause issue after
>>>> deployment if target node didn't use bootstrap kernel as environment kernel.
>>>>
>>>> So does target image will use bootstrap kernel as kernel image? If not,
>>>> how can I modify target kernel image?
>>>>
>>>> Many thanks,
>>>> Eddie.
>>>>
>>>> _______________________________________________
>>>> Mailing list: http://lists.openstack.org/cgi
>>>> -bin/mailman/listinfo/openstack
>>>> Post to     : openstack at lists.openstack.org
>>>> Unsubscribe : http://lists.openstack.org/cgi
>>>> -bin/mailman/listinfo/openstack
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170213/206ed166/attachment.html>