Hi Himanshu, For compute/worker node, please make sure Virtualization settings (such as VT-X and VT-D) ENABLED in BIOS. They are mandatory requirements for compute node. Regards, Yong From: Himanshu Goyal <himanshugoyal500@gmail.com> Date: Wednesday, 23 January 2019 at 6:33 PM To: "Hu, Yong" <yong.hu@intel.com> Cc: "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Deployment Option (error: compute boot in loop) Thanks a lot Juan and Yong, Able to see compute host in "system-host-list" after connecting with a hub. starlingX Compute installation has been done. But after unlocking the compute nodes the compute node come into an endless boot loop. dmesg log shows below error: [ 20.967137] iTCO_vendor_support: vendor-support=0 [ 20.968785] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 20.968840] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [ 21.066607] device-mapper: uevent: version 1.0.3 [ 21.067124] device-mapper: ioctl: 4.37.1-ioctl (2018-04-03) initialised: dm-devel@redhat.com<mailto:dm-devel@redhat.com> Checked the BIOS setting those are as mentioned in installation document. I'm using ISO Image available at below path: http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/ou... Regards, Himanshu Goyal On Tue, Jan 22, 2019 at 12:43 PM Hu, Yong <yong.hu@intel.com<mailto:yong.hu@intel.com>> wrote: Himanshu, Could you have a try with a hub which 2 mgt ports (from controller and compute) are plugged into? Let’s assure the normal setup works first, and then figure out why the direct linkage of cable doesn’t work. BTW: “worker” and “compute” are just different “personality” names in different STX version. On your current setup “compute” will do, supposedly. From: Himanshu Goyal <himanshugoyal500@gmail.com<mailto:himanshugoyal500@gmail.com>> Date: Tuesday, 22 January 2019 at 12:32 AM To: "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com<mailto:juan.carlos.alonso@intel.com>> Cc: "Hu, Yong" <yong.hu@intel.com<mailto:yong.hu@intel.com>>, "starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] Deployment Option Thanks Juan ,Yong I tried both the commands output shows as below: 1) [wrsroot@controller-0 ~(keystone_admin)]$ system host-add -n compute-0 -p worker -m 00:1e:67:fd:3d:fe usage: system host-add [-n <hostname>] [-p <personality>] [-s <subfunctions>] [-m <mgmt_mac>] [-i <mgmt_ip>] [-I <bm_ip>] [-T <bm_type>] [-U <bm_username>] [-P <bm_password>] [-b <boot_device>] [-r <rootfs_device>] [-o <install_output>] [-c <console>] [-v <vsc_controllers>] [-l <location>] [-D <true/false>] system host-add: error: argument -p/--personality: invalid choice: 'worker' (choose from 'controller', 'compute', 'storage', 'network', 'profile') [wrsroot@controller-0 ~(keystone_admin)]$ [wrsroot@controller-0 ~(keystone_admin)]$ 2) [wrsroot@controller-0 ~(keystone_admin)]$ system host-add -n compute-0 -p compute -m 00:1e:67:fd:3d:fe Host-add Rejected: Cannot add a compute host without specifying a mgmt_ip when static address allocation is configured. [wrsroot@controller-0 ~(keystone_admin)]$ Regards, Himanshu Goyal On Mon, Jan 21, 2019 at 8:42 PM Alonso, Juan Carlos <juan.carlos.alonso@intel.com<mailto:juan.carlos.alonso@intel.com>> wrote: Hi, The personality of computes changed to “worker”, so the command should be: system host-add -n compute-0 -p worker -m ${mac_address} Regards. Juan Carlos Alonso From: Hu, Yong Sent: Monday, January 21, 2019 8:51 AM To: Himanshu Goyal <himanshugoyal500@gmail.com<mailto:himanshugoyal500@gmail.com>>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com<mailto:juan.carlos.alonso@intel.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Deployment Option Hi Himanshu, “system host-list” doesn’t “see” your compute node and LLDP won’t work, because the mgt port on compute node directly connects to mgt port on controller-0 (rather than both connecting to a hub). Anyway, given you know the MAC of mgt port on compute node, you can have a try to run the following cmd: # system host-add -n compute-0 -p compute -m <compute_node_mgt_port_mac> Regards, yong From: Himanshu Goyal <himanshugoyal500@gmail.com<mailto:himanshugoyal500@gmail.com>> Date: Monday, 21 January 2019 at 8:14 PM To: "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com<mailto:juan.carlos.alonso@intel.com>> Cc: "starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] Deployment Option Thanks Juan, Able to unlock my controller node. But facing Issue in PXE boot of compute node. After unlocking of controller machine not able to see compute host in "system host-list" command. my controller machine is directly connected to compute machine. I'm following the below steps Steps: 1) system host-unlock controller-0 2) system host-list Output:: [wrsroot@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ 3) power on my compute machine. And give option to boot from PXE my compute machine is directly connected with controller with mgmt port. But not able to see host in "system host-list". 4) i tried with system host-add command also, but it is giving below error: Error: [wrsroot@controller-0 ~(keystone_admin)]$ system host-add Host-add Rejected: Cannot add a compute host without specifying a mgmt_ip when static address allocation is configured. Please suggest me the needful change. Regards, Himanshu Goyal