Re: [xcat-user] From where next-server is fetched from?
LOL. I feel like an idiot right now.
Hmmm thanks Kilian, you're indeed correct. I need to understand now why it
wasn't working and started working when I manually override the next-server
variable.
> On 21 May 2021, at 21:22, Kilian Cavalotti
> wrote:
>
> I don't think it needs to be expanded by xCAT in the DHCP lease file.
> dhcpd will literally send the
> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43; string in
> the DHCP reply, and the TFTP/PXE client will interpret this using the
> "next-server" value that is defined at the subnet level in dhcpd.conf.
>
> Some examples here: https://wiki.alpinelinux.org/wiki/PXE_boot#HOWTO
>
> Cheers,
> --
> Kilian
>
> On Fri, May 21, 2021 at 4:51 PM Vinícius Ferrão via xCAT-user
> wrote:
>>
>> Hello, I'm running xCAT development build and makedhcp is falling to proper
>> populate next-server on /var/lib/dhcpd/dhcpd.leases:
>>
>> As an example:
>>
>> host adano43 {
>> dynamic;
>> hardware ethernet 00:11:22:33:44:55;
>> uid 00:11:22:33:44:55;
>> fixed-address 172.26.0.43;
>>supersede server.ddns-hostname = "adano43";
>>supersede host-name = "adano43";
>>if option user-class-identifier = "xNBA" and option
>> client-architecture
>> = 00:00 {
>> supersede server.always-broadcast = 01;
>> supersede server.filename =
>> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43;;
>>} elsif option user-class-identifier = "xNBA" and option
>>client-architecture = 00:09 {
>> supersede server.filename =
>>
>> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43.uefi;;
>>} elsif option client-architecture = 00:07 {
>> supersede server.filename = "xcat/xnba.efi";
>>} elsif option client-architecture = 00:00 {
>> supersede server.filename = "xcat/xnba.kpxe";
>>} else {
>> supersede server.filename = "";
>>}
>> }
>>
>> So to figure it out, someone knows from where xCAT grabs the variable to
>> replace with the next-server? I know that this should be the management node
>> or maybe a service node, if I was using one.
>>
>> Thanks,
>> V.
>>
>> ___
>> xCAT-user mailing list
>> xCAT-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xcat-user
>
>
>
> --
> Kilian
>
>
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Ubuntu 18.04 SSH prompt
> On May 21, 2021, at 9:17 AM, Mark Gurevich wrote: > > > > What version of xCAT? The latest - 2.16.1 > > Can you show the lsdef of the node and lsdef of osimage ? [root@us7 ~]# lsdef m1 Object name: m1 arch=x86_64 bmc=172.29.1.74 bmcpassword=ADMIN bmcusername=ADMIN cons=ipmi consoleenabled=1 currchain=boot currstate=boot getmac=ipmi groups=all ip=172.29.0.74 mac=0c:c4:7a:f8:de:88 mgt=ipmi netboot=xnba os=ubuntu18.04.2 postbootscripts=otherpkgs postscripts=syslog,remoteshell,syncfiles,hardeths,mlnxofed_ib_install -p /install/ofed/MLNX_OFED_LINUX-5.1-2.5.8.0-ubuntu18.04-x86_64.iso profile=compute provmethod=ubuntu18.04.2-x86_64-install-compute serialport=1 serialspeed=115200 status=booted statustime=05-20-2021 13:08:08 [root@us7 ~]# lsdef -t osimage ubuntu18.04.2-x86_64-install-compute Object name: ubuntu18.04.2-x86_64-install-compute imagetype=linux osarch=x86_64 osname=Linux osvers=ubuntu18.04.2 otherpkgdir=/install/post/otherpkgs/ubuntu18.04.2/x86_64 pkgdir=/install/ubuntu18.04.2/x86_64 pkglist=/opt/xcat/share/xcat/install/ubuntu/compute.ubuntu18.04.x86_64.pkglist profile=compute provmethod=install template=/opt/xcat/share/xcat/install/ubuntu/compute.tmpl I found that if I add to the template (/opt/xcat/share/xcat/install/ubuntu/compute.tmpl) this line, the boot loader is installed automatically. d-i grub-installer/bootdev string /dev/sda I realize that that line is installing the MBR explicitly into /dev.sda, and if whatever reason /dev/sda isn't present, it won't work. So I'm sill wondering why the target location of MBR isn't calculated automatically. For he records, this is the output of lsblk: root@m1:~# lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 223.6G 0 disk |-sda18:10 243M 0 part /boot |-sda28:20 1K 0 part |-sda58:50 221.4G 0 part / `-sda68:60 1.9G 0 part [SWAP] nvme0n1 259:00 3.5T 0 disk `-nvme0n1p1 259:10 3.5T 0 part nvme2n1 259:20 3.5T 0 disk `-nvme2n1p1 259:50 3.5T 0 part nvme1n1 259:30 3.5T 0 disk `-nvme1n1p1 259:40 3.5T 0 part nvme3n1 259:60 3.5T 0 disk `-nvme3n1p1 259:10 0 3.5T 0 part nvme5n1 259:70 3.5T 0 disk `-nvme5n1p1 259:80 3.5T 0 part nvme4n1 259:90 3.5T 0 disk `-nvme4n1p1 259:11 0 3.5T 0 part > > Mark Gurevich > Poughkeepsie Development Lab > HPC Software Development - xCAT > > "If we knew what it was we were doing, it would not be called research, > would it?" > --Albert Einstein > > > > > > From: Michael Green > To: xCAT Users Mailing list > Date: 05/20/2021 03:17 PM > Subject: [EXTERNAL] Re: [xcat-user] Ubuntu 18.04 SSH prompt > > > > Yes, that was that! I reduced the debug to 1 and the ssh prompt is no > more. Thanks a lot for the tip! > > Next question: the installation now stops asking me where to install the > bootloader. > This prevents the installation from completing in unattended fashion. > > Where is that controlled in xcat? > > > ┌──┤ [!!] Install the GRUB boot loader on a hard disk > ├───┐ > │ > │ > │ You need to make the newly installed system bootable, by installing > │ > │ the GRUB boot loader on a bootable device. The usual way to do this > │ > │ is to install GRUB on the master boot record of your first hard > │ > │ drive. If you prefer, you can install GRUB elsewhere on the drive, or > │ > │ to another drive, or even to a floppy. > │ > │ > │ > │ The device should be specified as a device in /dev. Below are some > │ > │ examples: > │ > │ - "/dev/sda" will install GRUB to the master boot record of your > │ > │ first > │ > │hard drive; > │ > │ - "/dev/sda2" will use the second partition of your first hard > │ > │ drive; > │ > │ > │ > │ _ > │ > │ > │ > │ > │ > │ > │ > > └─┘ > > moves; selects; activates buttons > > On May 19, 2021, at 9:13 AM, Mark Gurevich > wrote: > > > > Do you by any chance have "xcatdebugmode" set in site table ? > > Mark Gurevich > Poughkeepsie Development Lab > HPC Software Development - xCAT > > "If we knew what it was we were doing, it would not be called > research, > would it?" > --Albert Einstein > > > > > > From: Michael Green > To: xCAT Users Mailing list > Date: 05/17/2021 07:20 PM > Subject: [EXTERNAL] [xcat-user] Ubuntu 18.04 SSH prompt > > > > Hello collective wisdom, > > Does anyone know how to disable the SSH prompt during diskfull > installation > of Ubuntu 18.04.5? > > > >┌───┤ [!!] Continue
Re: [xcat-user] From where next-server is fetched from?
I don't think it needs to be expanded by xCAT in the DHCP lease file.
dhcpd will literally send the
"http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43; string in
the DHCP reply, and the TFTP/PXE client will interpret this using the
"next-server" value that is defined at the subnet level in dhcpd.conf.
Some examples here: https://wiki.alpinelinux.org/wiki/PXE_boot#HOWTO
Cheers,
--
Kilian
On Fri, May 21, 2021 at 4:51 PM Vinícius Ferrão via xCAT-user
wrote:
>
> Hello, I'm running xCAT development build and makedhcp is falling to proper
> populate next-server on /var/lib/dhcpd/dhcpd.leases:
>
> As an example:
>
> host adano43 {
> dynamic;
> hardware ethernet 00:11:22:33:44:55;
> uid 00:11:22:33:44:55;
> fixed-address 172.26.0.43;
> supersede server.ddns-hostname = "adano43";
> supersede host-name = "adano43";
> if option user-class-identifier = "xNBA" and option
> client-architecture
> = 00:00 {
> supersede server.always-broadcast = 01;
> supersede server.filename =
> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43;;
> } elsif option user-class-identifier = "xNBA" and option
> client-architecture = 00:09 {
> supersede server.filename =
>
> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43.uefi;;
> } elsif option client-architecture = 00:07 {
> supersede server.filename = "xcat/xnba.efi";
> } elsif option client-architecture = 00:00 {
> supersede server.filename = "xcat/xnba.kpxe";
> } else {
> supersede server.filename = "";
> }
> }
>
> So to figure it out, someone knows from where xCAT grabs the variable to
> replace with the next-server? I know that this should be the management node
> or maybe a service node, if I was using one.
>
> Thanks,
> V.
>
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
--
Kilian
___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
[xcat-user] From where next-server is fetched from?
Hello, I'm running xCAT development build and makedhcp is falling to proper
populate next-server on /var/lib/dhcpd/dhcpd.leases:
As an example:
host adano43 {
dynamic;
hardware ethernet 00:11:22:33:44:55;
uid 00:11:22:33:44:55;
fixed-address 172.26.0.43;
supersede server.ddns-hostname = "adano43";
supersede host-name = "adano43";
if option user-class-identifier = "xNBA" and option client-architecture
= 00:00 {
supersede server.always-broadcast = 01;
supersede server.filename =
"http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43;;
} elsif option user-class-identifier = "xNBA" and option
client-architecture = 00:09 {
supersede server.filename =
"http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43.uefi;;
} elsif option client-architecture = 00:07 {
supersede server.filename = "xcat/xnba.efi";
} elsif option client-architecture = 00:00 {
supersede server.filename = "xcat/xnba.kpxe";
} else {
supersede server.filename = "";
}
}
So to figure it out, someone knows from where xCAT grabs the variable to
replace with the next-server? I know that this should be the management node or
maybe a service node, if I was using one.
Thanks,
V.
___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Ubuntu 18.04 SSH prompt
What version of xCAT? Can you show the lsdef of the node and lsdef of osimage ? Mark Gurevich Poughkeepsie Development Lab HPC Software Development - xCAT "If we knew what it was we were doing, it would not be called research, would it?" --Albert Einstein From: Michael Green To: xCAT Users Mailing list Date: 05/20/2021 03:17 PM Subject:[EXTERNAL] Re: [xcat-user] Ubuntu 18.04 SSH prompt Yes, that was that! I reduced the debug to 1 and the ssh prompt is no more. Thanks a lot for the tip! Next question: the installation now stops asking me where to install the bootloader. This prevents the installation from completing in unattended fashion. Where is that controlled in xcat? ┌──┤ [!!] Install the GRUB boot loader on a hard disk ├───┐ │ │ │ You need to make the newly installed system bootable, by installing │ │ the GRUB boot loader on a bootable device. The usual way to do this │ │ is to install GRUB on the master boot record of your first hard │ │ drive. If you prefer, you can install GRUB elsewhere on the drive, or │ │ to another drive, or even to a floppy. │ │ │ │ The device should be specified as a device in /dev. Below are some │ │ examples: │ │ - "/dev/sda" will install GRUB to the master boot record of your │ │ first │ │hard drive; │ │ - "/dev/sda2" will use the second partition of your first hard │ │ drive; │ │ │ │ _ │ │ │ │ │ │ │ └─┘ moves; selects; activates buttons On May 19, 2021, at 9:13 AM, Mark Gurevich wrote: Do you by any chance have "xcatdebugmode" set in site table ? Mark Gurevich Poughkeepsie Development Lab HPC Software Development - xCAT "If we knew what it was we were doing, it would not be called research, would it?" --Albert Einstein From: Michael Green To: xCAT Users Mailing list Date: 05/17/2021 07:20 PM Subject: [EXTERNAL] [xcat-user] Ubuntu 18.04 SSH prompt Hello collective wisdom, Does anyone know how to disable the SSH prompt during diskfull installation of Ubuntu 18.04.5? ┌───┤ [!!] Continue installation remotely using SSH ├───┐ │ │ │ Start SSH │ │ To continue the installation, please use an SSH client to connect to │ │ the IP address 172.29.0.74 fe80::ec4:7aff:fef8:de64 and log in as the │ │ "installer" user. For example: │ │ │ │ssh installer@172.29.0.74 │ │ │ │ The fingerprint of this SSH server's host key is: │ │ SHA256:+egqLvsAY5MN3/4ws6CBjj5Ro1bSEEvH2gzsfwBWv5g │ │ │ │ Please check this carefully against the fingerprint reported by your │ │ SSH client. │ │ │ │ │ │ │ └───┘ ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
