# Revision history [back]

By default, Packstack needs one node with a single NIC. See here.

You can then add a compute node. While the instructions say that you need two NICs, I remember faintly that it was possible with a single NIC. However, since your hosts are virtual, you can easily give them as many NICs as you like. I would use a different IP address range for the NICs.

After that, the first node still has both controller and compute roles. If you don’t want that, you can easily disable nova-compute.

By default, Packstack needs one node with a single NIC. See here.

You can then add a compute node. While the instructions say that you need two NICs, I remember faintly that it was possible with a single NIC. However, since your hosts are virtual, you can easily give them as many NICs as you like. I would use a different IP address range ranges for the NICs.NICs; less confusion.

After that, the first node still has both controller and compute roles. If you don’t want that, you can easily disable nova-compute.

By default, Packstack needs one node with a single NIC. See here.

You can then add a compute node. While the instructions say that you need two NICs, I remember faintly that it was possible with a single NIC. However, since your hosts are virtual, you can easily give them as many You could also work with VLANs or create extra NICs as you like. of the type eth0:0 on the compute host.

In case of several NICs, I would use different IP address ranges for the NICs; less confusion.NICs, to simplify troubleshooting. A single range probably works as well, but I am not sure about the ramifications.

After that, Once you have added your compute node, the first node still has both controller and compute roles. If you don’t want that, you can easily disable nova-compute.

By default, Packstack needs one node with a single NIC. See here.

You can then add a compute node. While the instructions say that you need two NICs, I remember faintly that it was possible with a single NIC. You could also work with VLANs or create extra NICs of the type eth0:0 on the compute host.

In case of several NICs, I would use different IP address ranges for the NICs, to simplify troubleshooting. A single range probably works as well, but I am not sure about the ramifications.

Once you have added your compute node, the first node still has both controller and compute roles. If you don’t want that, you can easily disable nova-compute.nova-compute: Either uninstall it, or use openstack compute service set --disable.