Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Dateuname -aNotes
7/13/20183.10.0-862.6.3.el7.x86_64 
8/8/20183.10.0-862.9.1.el7.x86_64 
8/28/20183.10.0-327.el7.x86_64Fresh install by ksa
8/29/20183.10.0-862.11.6.el7.x86_64 
10/4/20183.10.0-862.14.4.el7.x86_64 

 

On a new build, old or new hardware

  1.  check if firmware updates need to happen

    - BIOS, IDRAC, DISK/PERC

  2. NETDB needs for the node:

    a. NetDB must have these options:  --options filename=pxelinux.0,next-server=lnxpapa,tftp-server-name=lnxpapa

    b. NetDB must have dhcp enabled

    c. Determine the pxeboot-kickstart to use. There are many!

    and we should agree on which one to use. I'd recommend we make that part

    of the netdb record the way we do with some newer builds - I think it

    helps. See for instance comet2

    pxekickit: CentOS7/default.netboot.CentOS7.linux_desktop_2


    d. NetDB must have the MAC address

  3. Determine is there anything special about this machine that needs to be considered

    If this is rhel[56] node with a taylor.opts take a look and see if there

    is a one to one correstpondence between what taylor.opts is doing on the

    node and what we can do in chef.  For example, if the pre-cheffed node is

    using automounter, then all parties ( unix platform, the user)  need to know that no NFS native mounts are supported.

...