Can MultiNode mode be deployed to servers which only have 2 nics?

[tongda]

I tried to make experiments on OpenStack. The OVS_MultiNode mode needs a server with 3 nics, however, I have got only 3 workstations with 2 nics. Is there some solution to deploy it?

[hrushig]

you can use vlan for vm data network. your network will look like eth0 - managment eth0.700 - vm data network eth1 - public/external network

use ubuntu's vlan commands to create logical interface eth0.700 and configure your switch to allow tagged vlan 700.

Cheers ~hrushi

On Jun 25, 2013, at 6:41 PM, "tongda" notifications@github.com<mailto:notifications@github.com> wrote:

I tried to make experiments on OpenStack. The OVS_MultiNode mode needs a server with 3 nics, however, I have got only 3 workstations with 2 nics. Is there some solution to deploy it?

— Reply to this email directly or view it on GitHubhttps://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/issues/90.

[laboshinl]

I have got multinode grizzly cloud on Ubuntu with quantum(ovs) using 2 NICs (https://github.com/laboshinl/openstack-grizzly-cookbook), and single node installation on CentOS with Quantum using only 1 NIC (https://github.com/laboshinl/centos-cloud). Without any logical iface's. If this question is still actual I can explain.

[ghost]

laboshini, we're facing a situation as to where we can only have 1 (single) NIC per server - Our current biggest problem. We would very much like to install the multinode setup OSV, but it is not possible since it requires 3 NIC's. Do you have any experience or suggestions? Our current best bet is to attempt the Singlenode install with only 1 NIC. In folsom we had no issues with this because of Nova-network, but this has all changed. Our network requirements are not very difficult. Unfortunately though we are locked to only having 1 NIC on each server.

[laboshinl]

So, in few words: on every node you should install openvswitch, quantum-plugin. Create bridge br-int (without any ports). Configure quantum/server.conf like this:

             "DEFAULT auth_strategy keystone",
             "DEFAULT rpc_backend quantum.openstack.common.rpc.impl_qpid",
             "DEFAULT qpid_hostname #{node[:qpid][:ip]}",
             "DEFAULT allow_overlapping_ips True",
             "DEFAULT core_plugin quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2",
             "keystone_authtoken auth_host #{node[:keystone][:ip]}",
             "keystone_authtoken admin_tenant_name admin",
             "keystone_authtoken admin_user admin",
             "keystone_authtoken admin_password #{node[:admin][:password]}"]

ovs-plugin.conf:

              "DATABASE sql_connection mysql://quantum:#{node[:mysql][:password]}@#{node[:quantum][:ip]}/quantum",
             "SECURITYGROUP firewall_driver quantum.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver",
             "OVS enable_tunneling True",
             "OVS tenant_network_type gre",
             "OVS integration_bridge br-int",
             "OVS tunnel_bridge br-tun",
             "OVS tunnel_id_ranges 1:1000",
             "OVS local_ip #{node[:ipaddress]}"

On quantum node additionaly install all quantum-related packages, add bridge br-ex and add port eth0. That's all ;) More complex options you can get from here https://github.com/laboshinl/centos-cloud/blob/master/recipes/openvswitch.rb - on compute nodes. https://github.com/laboshinl/centos-cloud/blob/master/recipes/quantum.rb - on controller node, but it is a bit centos-oriented.

[ghost]

laboshini,

Thank you for the superior assistance! We actually had to revert to folsom because of other problems with the python base and the security layer we have. I will save your answer for the upgrades and return then, once again - In all respect, thank you!