Ask Your Question

thota's profile - activity

2015-05-07 04:16:41 -0600 received badge  Taxonomist
2014-07-22 21:08:20 -0600 received badge  Famous Question (source)
2014-07-22 21:08:20 -0600 received badge  Notable Question (source)
2014-04-11 11:59:27 -0600 received badge  Self-Learner (source)
2014-03-31 15:01:43 -0600 received badge  Famous Question (source)
2014-03-18 15:31:31 -0600 received badge  Famous Question (source)
2014-02-25 13:50:27 -0600 received badge  Notable Question (source)
2014-02-25 13:50:27 -0600 received badge  Famous Question (source)
2014-02-25 13:50:27 -0600 received badge  Popular Question (source)
2014-02-17 13:17:40 -0600 received badge  Famous Question (source)
2014-02-11 09:37:57 -0600 received badge  Notable Question (source)
2014-02-11 09:37:57 -0600 received badge  Popular Question (source)
2014-02-06 23:24:56 -0600 commented answer In multi nic environment, Only the first interface is coming up and getting its ip using DHCP. why?

Please find my update question above. Thanks !

2014-02-06 00:51:17 -0600 answered a question how to rename VIF interface (tap63ea2815-b5) created by openstack nova?

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 !

2014-02-06 00:49:00 -0600 commented question how to rename VIF interface (tap63ea2815-b5) created by openstack nova?

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. :)

2014-02-06 00:42:02 -0600 received badge  Popular Question (source)
2014-02-06 00:40:29 -0600 asked a question In multi nic environment, Only the first interface is coming up and getting its ip using DHCP. why?

Hello, I have a requirement to create virtual machines with four interfaces. So, I created four networks and assigned each network a subnet using "neutron". So far so good. When I lauch the virtual machine, I see only the first interface is up and getting its IP address using DHCP. Why are the other three interfaces not coming up and getting their IP addresses?

**Test Environment**  
openstack version - havana 
OS used on host machines - RHEL-6.4  

**Two node openstack setup** 
Controller - services: neutron dhcp agent, neutron ovs agent, neutron server 
Compute1 - services: nova compute, neutron ovs agent

I used below environment for creating networks and subnets.

export OS_USERNAME=admin
export OS_PASSWORD=changeit
export OS_TENANT_NAME=admin
export OS_AUTH_URL=http://controller:35357/v2.0

The way I created the networks is something below.

neutron net-create basenet_110 --provider:network_type vlan  --provider:physical_network basenet --provider:segmentation_id 110
neutron net-create basenet_111 --provider:network_type vlan  --provider:physical_network basenet --provider:segmentation_id 111

Please let me know, if you need more information. Thanks.

2014-02-06 00:26:23 -0600 received badge  Notable Question (source)
2014-02-06 00:26:23 -0600 received badge  Popular Question (source)
2014-01-10 00:13:36 -0600 answered a question neutron - not able to trunk vlan tags in to Virtual Machines

I could fix the problem - looks like the issue is with the kernel. When I enable vlan splinters everything worked well.

ovs-vsctl set interface eth11 other-config:enable-vlan-splinters=true
2014-01-08 03:19:03 -0600 asked a question neutron - not able to trunk vlan tags in to Virtual Machines

I'm trying to trunk vlan traffic in to the virtual machine, but failed to do so. Here is my requirement - An openstack setup with a controller and a compute node. compute node shall launch eight virtual machines using nova and each virtual machine shall run an application (telecom application). This application running on the virtual machine handles different types of traffic (for ex, management and data traffics). These traffics are differentiated with VLAN IDs. The compute node has a 10Gbps NIC (This interface is named as eth11 on my machine) and this interface receives the tagged data from the external switch.

OS on compute node is RHEL-6.4, so I followed the instructions as per document. Installed neutron on controller and compute nodes. I did not install "Network Node" as the virtual machines need not talk to external world (connect to internet).

Here is my configuration:

Controller Node:

/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini

tenant_network_type = vlan network_vlan_ranges = physnet1:100:300

Compute Node:

/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini

tenant_network_type = vlan network_vlan_ranges = physnet1:100:300 bridge_mappings = physnet1:br-eth11

Created a network

[root@controller ~]# neutron net-list +--------------------------------------+--------+------------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+------------------------------------------------------+ | 46d60b62-202e-460c-949d-b710db032ce0 | fabnet | de5a6015-2a10-4b3a-ae78-290ff621ffaa 192.168.12.0/24 | +--------------------------------------+--------+------------------------------------------------------+ [root@controller ~]# [root@controller ~]# neutron net-show 46d60b62-202e-460c-949d-b710db032ce0 +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | True | | id | 46d60b62-202e-460c-949d-b710db032ce0 | | name | fabnet | | provider:network_type | vlan | | provider:physical_network | physnet1 | | provider:segmentation_id | 100 | | router:external | False | | shared | False | | status | ACTIVE | | subnets | de5a6015-2a10-4b3a-ae78-290ff621ffaa | | tenant_id | 4b41b2c1ee3e42fcb928fadcf967bb1a | +---------------------------+--------------------------------------+

launched a VM:

[root@controller ~]# nova list +--------------------------------------+-------+--------+------------+-------------+---------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-------+--------+------------+-------------+---------------------+ | 8368dd7d-27b1-4721-af90-fb7d3c1eb13f | rhel1 | ACTIVE | None | Running | fabnet=192.168.12.3 | +--------------------------------------+-------+--------+------------+-------------+---------------------+

"ovs-vsctl show" ouput on compute node

[root@compute1 ~]# ovs-vsctl show 0bfed3e4-5f13-4726-a6a5-073fd47f1500 Bridge br-int Port "int-br-eth11" Interface "int-br-eth11" Port "tap56765470-5a" Interface "tap56765470-5a" Port br-int Interface br-int type: internal Bridge "br-eth11" Port "phy-br-eth11" Interface "phy-br-eth11" Port "br-eth11" Interface "br-eth11" type: internal Port "eth11" Interface "eth11" ovs_version: "1.11.0"

Assigned IP address to the br-eth11 interface and could ping to the virtual machine. Till here everything worked well.

Then, I added vlan subinterface to eth11 using vconfig vconfig add eth11 100 ifconfig eth11.100 192.168.100.24 up

Similarly added vlan subinterface to eth0 on virtual machine as below vconfig add eth0 100 ifconfig eth0.100.192.168.100.2 up

Now, when I try to ping from my compute node to 10.130.100.2 (eth0.100 on VM) I see " Destination Host Unreachable"

In the process I cleared tag for the port tap56765470-5a. This port was set to tag=2 by openstack and also deleted vlan related flows created by openstack. Below were the flows created by openstack

[root@compute1 ~]# ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=6496.181s, table=0, n_packets=88, n_bytes=3936, idle_age=1, priority=3,in_port=21,dl_vlan=100 actions=mod_vlan_vid:2,NORMAL cookie=0x0, duration=8298.765s, table=0, n_packets=177, n_bytes=19646, idle_age=176, priority=0 actions=NORMAL

[root@compute1 ~]# ovs-ofctl dump-flows br-eth11 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=6628.074s, table=0, n_packets=41, n_bytes=7910, idle_age=5751, priority=4,in_port=2 ... (more)

2014-01-06 05:21:36 -0600 commented question neutron - Not able to ping virtual machine from host

I got the information from openvswitch FAQ. "There is no compelling reason why Open vSwitch must work this way.However, this is the way that the Linux kernel bridge module has always worked, so it's a model that those accustomed to Linux bridging are already used to. Also, the model that most people expect is not implementable without kernel changes on all the versions of Linux that Open vSwitch supports."

2014-01-06 05:10:24 -0600 asked a question neutron - Not able to ping virtual machine from host

I have a requirement from a customer (telecom application) that - Eight virtual machines are launched on a compute node using openstack nova and each virtual machine shall run the telecom application. The telecom application running on the virtual machine handles different types of traffic (for ex, management and data traffics). These traffics are differentiated with VLAN IDs. The compute node has a 10Gbps NIC that receives the tagged data.

With this, I want to create a OVS that shall trunk the tagged traffic into the virtual machine. That is, OVS should not strip the vlan tag and the application on the VM should see the vlan tag to differentiate the traffic.

Now, to start with, I want to establish communication between host (compute) and VM using OVS. In simple, I should be able to ping the virtual machine from the host (compute1) through OVS. For this, I created OVS bridge "br-int" and created a network using openstack neutron and launched a virtual machine. openstack nova created a tap interface (tap63ea2815-b5) that got connected to eth0 in the virtual machine and to OVS on the compute node. Later I added eth11 interface (10Gbps NIC on compute/host) to the ovs bridge.

Configured both eth11 (on the host/compute) and eth0 on the virtual machine in the same subnet. I’m not able to ping the VM from the host.

But, If I remove the IP address on eth11 and assign it to br-int, then I’m able to ping the virtual machine.

Can someone explain the behavior.

Below is “ovs-vsctl show” output [root@compute1 ~]# ovs-vsctl show 0bfed3e4-5f13-4726-a6a5-073fd47f1500 Bridge br-int Port "eth11" Interface "eth11" Port "tapb62b2a46-71" Interface "tapb62b2a46-71" Port br-int Interface br-int type: internal ovs_version: "1.11.0"

Thanks in advance.

2014-01-05 04:37:15 -0600 asked a question how to rename VIF interface (tap63ea2815-b5) created by openstack nova?

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?

2013-12-29 12:14:56 -0600 received badge  Notable Question (source)
2013-12-21 05:52:54 -0600 received badge  Teacher (source)
2013-12-21 05:52:54 -0600 received badge  Self-Learner (source)
2013-12-21 05:51:40 -0600 received badge  Popular Question (source)
2013-12-21 02:11:39 -0600 answered a question how to configure multiple interfaces to virtual machine instance using compute nova (multinic support)

I could fix this - as described below.

compute1 Node details: Host OS: RHEL-6.4 Two Physical Network devices for Internal data communication (eth10 and eth11) and one (eth4) to connect to external network, Internet. Network Manager used: FlatDHCPManager

/etc/nova/nova.conf file
 network_manager           nova.network.manager.FlatDHCPManager
firewall_driver                 nova.virt.libvirt.firewall.IptablesFirewallDriver 
 network_size                  254
 allow_same_net_traffic   False
 multi_host                      True
 send_arp_for_ha             True
 share_dhcp_address        True
 force_dhcp_release         True
 flat_interface                 eth11
flat_network_bridge         brfab2
 public_interface              eth4

From "controller" issued below command to create two networks.
# nova network-create vmnet_fab1 --fixed-range-v4=192.168.11.0/24  --bridge=brfab1 --bridge-interface=eth10 --multi-host=T
# nova network-create vmnet_fab2 --fixed-range-v4=192.168.12.0/24  --bridge=brfab2 --bridge-interface=eth11 --multi-host=T 

list the networks. Below command lists the above created network id's, say net_id_1 and net_id_2.
# nova network-list


Now, boot the Virtual Machine -
# nova boot --flavor <flavor_id> --key_name <ssh_key> --image <image_id> --security_group default --nic net-id=<net_id_1> --nic net-id=<net_id_2>

A virtual machine is launched with two network interfaces, one connected to vnet_fab1 and other connected to vnet_fab2.

That's all !

2013-12-20 23:08:18 -0600 received badge  Supporter (source)
2013-12-19 21:15:57 -0600 received badge  Editor (source)
2013-12-19 21:13:41 -0600 asked a question how to configure multiple interfaces to virtual machine instance using compute nova (multinic support)

I have two node setup - controller and a compute1. The compute1 node has got two NICs and I want to create two flat networks using nova network as described in http://docs.openstack.org/admin-guide-cloud/content/ch_introduction-to-openstack-compute.html#section_use-multi-nics (multinic support). The other way, I want to configure two interfaces to a virtual machine instance. I could create one flat network using FlatDHCPManager as described in openstack documentation but facing problems while configuring two flat networks for two NICs. Firstly, I'm not sure how to configure nova.conf to configure "flat_network_bridge" and "flat_interface" for two NICs? could someone here help in configuring the same. Thanks in advance.

Best Prashanth

2013-12-17 00:55:59 -0600 received badge  Enthusiast
2013-12-03 23:05:35 -0600 commented answer Unable to Login to Openstack Dashboard (Havana)

Issue got fixed by following comments below and so added my answer below, yesterday.

2013-12-03 04:37:40 -0600 answered a question Unable to Login to Openstack Dashboard (Havana)

I encountered exactly the same issue while on RHEL-6.4. I could get rid off the issue by disabling SELINUX and modifying OPENSTACK_KEYSTONE_DEFAULT_ROLE as mentioned above. Thank you all for your help.