Ask Your Question

Revision history [back]

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

EDIT: Install the controller by following the quickstart page. It works as-is.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

EDIT: Install the controller by following the quickstart page. It works as-is.as-is. Then use the add a compute host page, but don't follow it by the letter, as it is outdated.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

EDIT: Install the controller by following the quickstart page. It works as-is. as-is. Personally, I added the following options to the packstack command:

  • -d for debug messages, useful if something goes wrong
  • --default-password=myfavouritepassword. Otherwise, Packstack generates unreadable passwords; good for production, bad for experimentation

Then use the add a compute host page, but don't follow it by the letter, as it is outdated.

outdated. Changes:

  • Ignore the paragraph Adjust network card names. A single network interface is sufficient.
  • Ignore the paragraph Skip installing on an already existing servers

Caveat: I used two Virtualbox machines, each with a single NIC, rather than physical PCs.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

EDIT: Install the controller by following the quickstart page. It works as-is. Personally, I added the following options to the packstack command:

  • -d for debug messages, useful if something goes wrong
  • --default-password=myfavouritepassword. Otherwise, Packstack generates unreadable passwords; good for production, bad for experimentation

Then use the add a compute host page, but don't follow it by the letter, as it is outdated. letter. Changes:

  • Ignore the paragraph Adjust network card names. A single network interface is sufficient.sufficient, and CONFIG_NEUTRON_OVS_TUNNEL_IF can be left alone.
  • Ignore the paragraph Skip installing on an already existing servers. In my experience, when you exclude the controller, thinking that it is already installed, certain components will be missing on it later.

Caveat: I used two Virtualbox machines, each with a single NIC, rather than physical PCs.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

EDIT: Install the controller by following the quickstart page. It works as-is. Personally, I added the following options to the packstack command:

  • -d for debug messages, useful if something goes wrong
  • --default-password=myfavouritepassword. Otherwise, Packstack generates unreadable passwords; good for production, bad for experimentation

Then use the add a compute host page, but don't follow it by the letter. Changes:

  • Ignore the paragraph Adjust network card names. A single network interface is sufficient, and CONFIG_NEUTRON_OVS_TUNNEL_IF can be left alone.
  • Ignore the paragraph Skip installing on an already existing servers. In my experience, when you exclude the controller, thinking that it is already installed, certain components will be missing on it later.

Until recently, the add a compute host page assumed Nova-Network instead of Neutron, but that seems to have been updated.

Caveat: I used two Virtualbox machines, each with a single NIC, rather than physical PCs.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

EDIT: Install the controller by following To install the controller, just follow the quickstart page. It works as-is. Personally, I added the following options to the packstack command:

  • -d for debug messages, useful if something goes wrong
  • --default-password=myfavouritepassword. Otherwise, Packstack generates unreadable passwords; good for production, bad for experimentation

Then use the add a compute host page, but don't follow it by the letter. Changes:

  • Ignore the paragraph Adjust network card names. A single network interface is sufficient, and CONFIG_NEUTRON_OVS_TUNNEL_IF can be left alone.
  • Ignore the paragraph Skip installing on an already existing servers. In my experience, when you exclude the controller, thinking that it is already installed, certain components will be missing on it later.

Until recently, the add a compute host page assumed Nova-Network instead of Neutron, but that seems to have been updated.

Caveat: I used two Virtualbox machines, each with a single NIC, rather than physical PCs.

If you want to follow the install guide to the letter, you need two NICs. I think it should work with VLAN interfaces - instead of two NICs, create two VLAN interfaces on a physical NIC.

If your goal is to learn, try out the VLANs or simply put all addresses on the same NIC. If your goal is to have a functioning cloud, try Packstack. It works very well with a single NIC.

EDIT: To install the controller, just follow the quickstart page. It works as-is. Personally, I added the following options to the packstack command:

  • -d for debug messages, useful if something goes wrong
  • --default-password=myfavouritepassword. Otherwise, Packstack generates unreadable passwords; good for production, bad for experimentation

Then provision your second machine with Centos and use the add a compute host page, but don't follow it by the letter. Changes:

  • Ignore the paragraph Adjust network card names. A single network interface is sufficient, and CONFIG_NEUTRON_OVS_TUNNEL_IF can be left alone.
  • Ignore the paragraph Skip installing on an already existing servers. In my experience, when you exclude the controller, thinking that it is already installed, certain components will be missing on it later.

Later, you can add more compute hosts in the same way. It's very convenient. In my virtual environment, the controller took about 30 min, each compute host 20-25 min to set up.

Until recently, the add a compute host page assumed Nova-Network instead of Neutron, but that seems to have been updated.

Caveat: I used two Virtualbox machines, each with a single NIC, rather than physical PCs.