Ask Your Question
0

OvS, VXLAN, and live migration

asked 2016-12-19 21:28:52 -0500

fifi gravatar image

updated 2016-12-21 13:28:45 -0500

Hi,

I have a 4-node openstack JUNO cluster (1 controller, 1 network and 2 computes). Live migration and vxlan has been configured on it successfully. I'm gonna add the third compute node through a virtual router (OVS and a controller) to the existing cluster for some live migration experiments over vxlan.

I wonder which network should be used for this? 'vm tarffic' network or 'management' network? Migration, by default, uses management network. However, when I check my ovs bridges on compute nodes I see vxlan ports has been set up on 'vm traffic' network not 'management' network.

I'd like to know where I need to put my virtual router to set up a vxlan tunnel for live vm migration between my new and those two old compute nodes?(migration over L3 networks)

Besides, i need to know wether enabling vxlan on my compute nodes will be enough or I need to enable vxlan interfaces on my virtual router (between my compute nodes) as well?

Thanks

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-12-19 23:53:24 -0500

updated 2016-12-19 23:53:53 -0500

You seem to be confusing the network infrastructure underlying OpenStack, which includes the management and VM networks, with the virtual networks created by OpenStack (or I am confused by what you write).

When you migrate an instance, it is copied over an infrastructure network, usually Management. Since Mitaka, dedicated migration networks are also supported in order to reduce the load on Management (http://specs.openstack.org/openstack/...).

The VXLAN ports you mention were created to implement the virtual networks to which instances are connected. You don't migrate over virtual networks.

Most likely you should use Management for migration. It's the default, and it doesn't require any configuration.

edit flag offensive delete link more

Comments

For VXLAN we need to setup VTEPs on both sides. On my openstack, these VTEPs are configured on the OVS ports which is in control of physical Ethernets on 'vm network'

fifi gravatar imagefifi ( 2016-12-20 14:27:42 -0500 )edit

Since you say that no VXLAN interfaces have been set up for the management network, I conclude that the management network is not based on a VXLAN tunnel, but your VM network is. Perhaps it is that fact that you need to change. I hope I am not totally confused though.

Bernd Bausch gravatar imageBernd Bausch ( 2016-12-20 21:35:01 -0500 )edit

So you mean I need to use vm network for migration not the management?

fifi gravatar imagefifi ( 2016-12-20 23:42:01 -0500 )edit

I think you should use management, but you seem to insist that you want to use a VXLAN connection for migration, and from your description, Management is not a VXLAN. And I am most likely confused!

Bernd Bausch gravatar imageBernd Bausch ( 2016-12-21 04:32:33 -0500 )edit

To clarify, I performed live migration in a L2 domain in my openstack cluster successfully. Now, I add another compute node to my old openstack cluster. However, this new compute node is connected to the old cluster via a router. Now my old cluster and new compute node are in two separate L3 domains

fifi gravatar imagefifi ( 2016-12-21 11:01:36 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-12-19 21:28:52 -0500

Seen: 335 times

Last updated: Dec 21 '16