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> 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>; Alonso, Juan Carlos < juan.carlos.alonso@intel.com> *Cc:* 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> *Date: *Monday, 21 January 2019 at 8:14 PM *To: *"Alonso, Juan Carlos" <juan.carlos.alonso@intel.com> *Cc: *"starlingx-discuss@lists.starlingx.io" < 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
On Fri, Jan 18, 2019 at 10:01 PM Alonso, Juan Carlos < juan.carlos.alonso@intel.com> wrote:
Hi,
Good that you could resolve config_controller issue.
I am not sure if you can avoid/skip extra configuration for hosts you don’t want during config_controller. I think you need to follow the installation steps normally but provision only the host you want to use.
Yesterday I asked to my team and it is possible to deploy 1 controller and 1 compute only, please refer to https://github.com/xe1gyq/starlingx/blob/master/ControllerStorage.md
To configure cinder on controller-0 you need to have a partition with space available to be added to cinder-volume. By default should be two partitions on each host, one with available space.
Regards.
Juan Carlos Alonso
*From:* Himanshu Goyal [mailto:himanshugoyal500@gmail.com] *Sent:* Thursday, January 17, 2019 11:16 PM *To:* Alonso, Juan Carlos <juan.carlos.alonso@intel.com> *Cc:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] Deployment Option
Thanks Juan,
Error is resolved after again boot the server. The reason for that my management interface was not up.
I have some Questions:
1) As I'm deploying starlingX with only 1 controller & 1 compute Machine.while executing "sudo config_controller" it is taking the IP Addresses of controller 0, controller 1 & floating IP Address. As i have only one controller, So how can i avoid those type of configurations..?
2) Is there any specific installation guide for that(1 controller & 1 compute) type installation currently I'm following the guide: https://docs.starlingx.io/installation_guide/controller_storage.html#control.... Please suggest me the need full changes i have to done for that.
3) my controller machine have one Disk of around 3725GB, But when I'm trying to configure cinder on same disk host-disk-list command shows me available disk is as 0 GB. please suggest me if there anyway to use that same disk with cinder.
*snapshot of host-disk-list:*
[image: image.png]
Regards,
Himanshu Goyal
On Thu, Jan 17, 2019 at 8:41 PM Alonso, Juan Carlos < juan.carlos.alonso@intel.com> wrote:
Hi,
On what step of config_controller it is failing? Can you provide the logs?
Are you deploying manually or automatic?
To apply the config_controller again I think you need to start over the installation process.
Regards.
Juan Carlos Alonso
*From:* Himanshu Goyal [mailto:himanshugoyal500@gmail.com] *Sent:* Thursday, January 17, 2019 7:22 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] Deployment Option
Hi,
I'm trying to install StarlingX Controller 0 on Physical Machine, But it is failing in config_controller at task* waiting for service activation* ......
with Error: "*Configuration failed: Timeout waiting for service enable*"
I'm using ISO available at the path: http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/ou...
Please suggest us the procedure to debug that & how i can re-run the config_controller again.
Many Thanks,
Himanshu Goyal
On Tue, Jan 1, 2019 at 3:34 PM Himanshu Goyal <himanshugoyal500@gmail.com> wrote:
Hi,
Can we deploy starlingX with 2 Machines 1 controller & 1 Compute Node (Both nodes on different physical Machines).
Many Thanks,
Himanshu Goyal
