Closed beekhof closed 8 years ago
Oh, and interestingly, the compute node is named compute_2
not compute_0
:
7836 ? Sl 1:12 /usr/libexec/qemu-kvm -name compute_2 -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu host -m 6144 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid e46d79f9-fefc-4b56-8667-12f9345e1f62 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/stack/.config/libvirt/qemu/lib/domain-compute_2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot menu=off,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x3 -device ahci,id=sata0,bus=pci.0,addr=0x4 -drive file=/home/stack/.quickstart/pool/compute_2.qcow2,if=none,id=drive-sata0-0-0,format=qcow2,cache=unsafe -device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -netdev tap,fd=22,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:d1:ec:9a:b2:39,bus=pci.0,addr=0x2 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
Sorry I missed this, the code has moved to https://github.com/openstack/tripleo-quickstart
That doesnt matter for this particular issue though.
If you do ironic node-list
before deploying, you will see that you have all of your nodes in Ironic. If not, that would be a pretty surprising bug. Please file it at https://bugs.launchpad.net/tripleo-quickstart I would be interested to investigate that further.
In any case, in order to actually deploy to those extra nodes, we need to pass an extra argument to the deploy command.
In the ha config file, there is an extra_args key, those are arbitrary arguments passed to the openstack overcloud deploy
command. You could add --compute-scale 3 to that to get all 3 compute nodes to deploy. Note that you will need a pretty heavy duty virthost to deploy 6 nodes. I would guess at least 64GB of RAM.
Ugh, I was just missing --compute-scale 3
Ah, which I see you just recommended. Machine is reasonably beefy, 8x Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz (quad core) but "only" 32Gb RAM. Not much choice if I need to work on instance HA though :)
Does it have SSD? Might be able to get away with swap + KSM if it has SSD. Otherwise, I would be pretty surprised if something doesnt get OOM killed during deploy. The box I have is about those specs, and even with KSM, it struggles with 3 control 1 compute 1 ceph. Happy to help troubleshoot if you hit deploy issues though.
If I add two extra compute nodes to ha.yaml, ie:
instackenv
contains all 6 nodes however I still only end up with one compute node after running./overcloud-deploy.sh
Any pointers where I should start looking?