Ask Your Question
0

how to rename VIF interface (tap63ea2815-b5) created by openstack nova? [closed]

asked 2014-01-05 04:37:15 -0500

thota gravatar image

Had two node openstack environment with a controller and a compute1 nodes. I Created a network using neutron and launched a VM on compute1. This created a vif interface with 14 characters long (tap63ea2815-b5). I want to create a VLAN subif on this vif interface (tap63ea2815-b5) using vconfig. For example I created a subif for VLAN 200 using "vconfig add tap63ea2815-b5 200". This should create an interface with the name "tap63ea2815-b5.200". But because the length of vif is 14 characters and maximum length supported by Linux OS is 16 characters, the interface is created as "tap63ea2815-b5." (an extra dot to the original name). With this I'm not able to create more than one VLAN subif's.

I want to choose a shorter name for the vif interface. Is there a way to configure the vif interface name?

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by dheeru
close date 2014-02-06 05:43:35.163809

Comments

In general you don't want to mess about with the devices created by OpenStack. If you can tell us what you're actually trying to accomplish we can probably provide you with a better solution. http://www.catb.org/~esr/faqs/smart-questions.html has some suggestions on how to ask questions, including http://www.catb.org/~esr/faqs/smart-questions.html#goal, which is especially relevant.

larsks gravatar imagelarsks ( 2014-01-05 12:47:44 -0500 )edit

larsks, thanks for pointing me to a nice document. The issue was "openvswitch vlan splinters". I was not aware of Linux kernel bugs related to openvswitch and haven't enabled "vlan splinters", instead tried to create vlan sub-interface on the "tap" interface. Now, All is well. :)

thota gravatar imagethota ( 2014-02-06 00:49:00 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-02-06 00:51:17 -0500

thota gravatar image

The issue was "openvswitch vlan splinters". I was not aware of Linux kernel bugs related to openvswitch and haven't enabled "vlan splinters". On enabling it, everything went well !

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-01-05 04:37:15 -0500

Seen: 203 times

Last updated: Feb 06 '14