[Rdo-list] [RDO-Manager] IBM H-Chassis install bare metal
dsimmons at krozak.com
Tue Nov 10 15:46:01 UTC 2015
So I got the fake-pxe driver to do the inspection run and the results are reported back to the undercloud node. I see the information has been updated with ironic node-show. I was able to set the provision status and the node is now available. Thanks for the help.
From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Dmitry Tantsur
Sent: Monday, November 9, 2015 12:13 PM
To: rdo-list at redhat.com
Subject: Re: [Rdo-list] [RDO-Manager] IBM H-Chassis install bare metal
On 11/09/2015 05:58 PM, Hugh O. Brock wrote:
> On Mon, Nov 09, 2015 at 08:45:56AM -0800, David Simmons wrote:
>> Thanks for responding.
>> That part I understand and have that working right. The issue I am having is configuring RDO Manager/Ironic to work.
>> In the undercloud.conf file, you specify the local interface. This seems to be used for both PXE boot and IPMI operations. When the undercloud is installed, the networking is not being configured correctly. If the tagged interface isn't set up correctly, I lose access to the AMM and subsequently the IMM of the individual blade.
>> If I could get Ironic to not perform the IPMI operations and I have to reboot manually, that would be fine but I don't seem to see how to do that in the documentation.
> There is a "fake_pxe" driver for Ironic that does exactly this --
> basically, no-ops all the power management stuff. I don't know exactly
> how you turn it on but a google should help.
didn't try it, but should be something like:
1. add it to 'enabled_drivers' in ironic.conf 2. restart conductor(s) 3. create nodes with this driver and don't forget to reboot them when needed (look at the virtual console to figure out)
>> -----Original Message-----
>> From: Marius Cornea [mailto:marius at remote-lab.net]
>> Sent: Monday, November 9, 2015 11:26 AM
>> To: David Simmons <dsimmons at krozak.com>
>> Cc: rdo-list at redhat.com
>> Subject: Re: [Rdo-list] [RDO-Manager] IBM H-Chassis install bare
>> If I understand it correctly you could set up the undercloud 1G port as trunk, use untagged frames for management and tagged for the Chassis Internal Network VLAN.
>> Here are some instructions to set up a vlan tagged interface:
>> On Mon, Nov 9, 2015 at 3:45 PM, David Simmons <dsimmons at krozak.com> wrote:
>>> I am installing RDO via RDO-Manager on a set of IBM H-Chassis blades.
>>> I need to configure the networking to perform the IPMI operations
>>> and PXE boot the overcloud nodes. The problem I am trying to solve
>>> is to get the chassis AMM to correctly route the IPMI/PXE operations
>>> to the blades. The IBM chassis requires all IPMI networking to use
>>> a VLAN that has been specified as the Chassis Internal Network. I
>>> have installed the undercloud on on blade on CentOS 7 and have been able to interact with the AMM and the blade
>>> IMMs on a vlan. Where I am running into problems is when the undercloud
>>> configuration occurs I am no longer able to interact on the
>>> specified VLAN and lose access to the Chassis AMM.
>>> On each blade I have 4 network ports. 2 1G and 2 10G network
>>> switches. I have installed CentOS on the undercloud and use 1 1G
>>> port as the management. I have specified a 10G switch as the PXE/Management network.
>>> In the undercloud.conf file the 10G port is the port I have
>>> specified as the local interface.
>>> To use the IPMI interface it has to tag all packets with the Chassis
>>> Internal Network VLAN. Are there any configuration tips that I can follow?
>>> David Simmons
>>> Rdo-list mailing list
>>> Rdo-list at redhat.com
>>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> To unsubscribe: rdo-list-unsubscribe at redhat.com
Rdo-list mailing list
Rdo-list at redhat.com
To unsubscribe: rdo-list-unsubscribe at redhat.com
More information about the rdo-list