Thank you all so much.
On Fri, Jul 10, 2015 at 09:40 Jarrod Johnson jjohns...@lenovo.com wrote:
Oh, btw, does nodels nodes vpd.serial give you what you expect?
If you want to do it, there's not a particularly well built in, but to
make a script that would do it:
# rinv n2-n4
Oh, btw, does nodels nodes vpd.serial give you what you expect?
If you want to do it, there's not a particularly well built in, but to make a
script that would do it:
# rinv n2-n4 serial|grep System | sed -e 's/^/nodech /' -e 's/: System Serial
Number: / nodepos.comments=/'
nodech n3
As of today we are not using nodepos table for anything. I started
experimenting and while adding nodepos.rack, nodepos.chassis, and
nodepos.height values are easy to add using nodech command, things that are
different between nodes are not that easy to enter without a lot of manual
data entry.
I don't know exactly what the full scheme is, so I'll give an example where the
values can be derived from the name:
(assuming nodes are 72 in the bottom 36u and you want u to flow rack to rack):
subtract 5001, then divide by 2 since they are two nodes per u, take the
remainder when divided by
Hello Wang,
Thank you for the interaction.
*From my point view that you should consider the bare-metal and virtual
machine management to be two levels.*
Agreed, though I want xCAT to have node definitions for both levels,
because I want OS deployment to be handled by xCAT for ESXi and for our
FYI, xCAT's vm commands don't require vCenter, though certain functions like
rmigrate and friends are restricted by vmware. Unless the free license is
installed, after which ESXi locks us out of the API (eval mode does not have
this restriction).
So if you stateless boot or install with a
Jarrod,
Thanks for the reply.
*FYI, xCAT's vm commands don't require vCenter, though certain functions
like rmigrate and friends are restricted by vmware. Unless the free
license is installed, after which ESXi locks us out of the API (eval mode
does not have this restriction).*
Below is a
