Open Stack

(Resending after stripping the image out for the mailing list, hopefully!)

Well, I <3 that your using the ironic horizon plugin!

Can you confirm the contents of the flavors you are using for
scheduling, specifically the capabilities field.

Are you using whole disk images, or are you using partition images?

On Wed, Sep 16, 2020 at 2:13 PM Tyler Bishop <tbishop at liquidweb.com> wrote:
>
> Hi Julia,
>
> All of these are latest stable train using Kolla-ansible.
>
> I am using local disk booting for all deployed instances and we utilize neutron networking with plans.
>
> Attached screenshot of driver config.
>
> On Sep 16, 2020, 2:53 PM -0400, Julia Kreger <juliaashleykreger at gmail.com>, wrote:
>
> I guess we need to understand if your machines are set to network boot
> by default in ironic's configuration? If it is set to the flat
> network_interface and the instances are configured for network
> booting? If so, I'd expect this to happen for a deployed instance.
>
> Out of curiosity, is this master branch code? Ussuri? Are the other
> environments the same?
>
> -Julia
>
> On Wed, Sep 16, 2020 at 11:33 AM Tyler Bishop <tbishop at liquidweb.com> wrote:
>
>
> Normally yes but I am having the PXE added to NON provision ports as well.
>
> I tore down the dnsmasq and inspector containers, rediscovered the hosts and it hasn’t came back.. but that still doesn’t answer how that could happen.
> On Sep 16, 2020, 3:53 AM -0400, Mark Goddard <mark at stackhpc.com>, wrote:
>
> On Tue, 15 Sep 2020 at 20:13, Tyler Bishop <tbishop at liquidweb.com> wrote:
>
>
> Hi,
>
> My issue is i have a neutron network (not discovery or cleaning) that is adding the PXE entries for the ironic pxe server and my baremetal host are rebooting into discovery upon successful deployment.
>
> I am curious how the driver implementation works for adding the PXE options to neutron-dhcp-agent configuration and if that is being done to help non flat networks where no SDN is being used? I have several environments using Kolla-Ansible and this one seems to be the only behaving like this. My neutron-dhcp-agent dnsmasq opt file looks like this after a host is deployed.
>
> dhcp/7d0b7e78-6506-4f4a-b524-d5c03e4ca4a8/opts cat /var/lib/neutron/dhcp/ffdf5f9b-b4ad-4a53-b154-69eb3b4a81c5/opts
> tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:dns-server,10.60.3.240,10.60.10.240,10.60.1.240
> tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:classless-static-route,169.254.169.254/32,10.60.66.2,0.0.0.0/0,10.60.66.1
> tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,249,169.254.169.254/32,10.60.66.2,0.0.0.0/0,10.60.66.1
> tag:subnet-57b772c1-7878-4458-8c60-cf21eac99ac2,option:router,10.60.66.1
> tag:port-08908db1-360b-4973-87c7-15049a484ac6,150,10.60.66.11
> tag:port-08908db1-360b-4973-87c7-15049a484ac6,210,/tftpboot/
> tag:port-08908db1-360b-4973-87c7-15049a484ac6,66,10.60.66.11
> tag:port-08908db1-360b-4973-87c7-15049a484ac6,67,pxelinux.0
> tag:port-08908db1-360b-4973-87c7-15049a484ac6,option:server-ip-address,10.60.66.11
>
>
> Hi Tyler, Ironic adds DHCP options to the neutron port on the
> provisioning network. Specifically, the boot interface in ironic is
> responsible for adding DHCP options. See the PXEBaseMixin class.