Ask Your Question

vikrant's profile - activity

2017-06-09 02:43:08 -0600 received badge  Necromancer (source)
2017-06-07 04:52:31 -0600 answered a question Ceilometer - Error: An error occurred. Please try again later
2017-06-07 04:49:38 -0600 answered a question errors with ceilometer-central and ceilometer-agent-compute
2017-06-07 04:44:32 -0600 commented question time taked by ceilometer to change alarm state in autoscaling

what is the configuration of alarm? value of period & evaluation-periods?

2017-05-04 08:27:22 -0600 commented answer Unable to create security group.

Hi, are you able to solve this issue, i am facing the same. Help me to fix it.

2017-04-28 02:14:32 -0600 commented answer Ceilometer some meters missing

Hi Mohit, can you explain a bit more how to add stack for scaleup_policy & cpu_alarm_high policy on .yaml file.

2017-04-25 05:47:30 -0600 commented answer Ceilometer Alarm insufficient Data

@AB239 - are you able to solve the issue, i am also facing the same issue. Help me me if you got it fixed.

2016-04-19 06:42:17 -0600 answered a question how does nova decide the VM nic type?

Please check the ports under br-int bridge using the command "ovs-vsctl show". It should be vhostuser ports, you can check the type it should be "vhuXXXXX".

For ovs-dpdk plugin the ports are of type vhostuser on the host. Inside the VM they appear as virtio-net ports. vhostuser driver is not a self-contained virtio device implementation. It uses virtio driver to communicate with guest.

2016-04-13 12:47:22 -0600 received badge  Teacher (source)
2016-04-13 04:45:47 -0600 answered a question Performance Monitoring counters

As i know some of the perf counters are different for different CPU model, perhaps they have different name for the same counters. As in your case Guest and Host CPU models are different. You can make guest CPU model same as Host - In nova.conf add cpu_mode=host-model

2016-03-16 00:17:09 -0600 answered a question no internet connection in VMs running in devstack (Single Node)

As the output of "ovs-vsctl show" shows that, there is no physical port (ex- eth0 or eth1 ) is associated with br-ex. First You need to have a physical port associated with the external bridge, then associate the floating point IP to the VM through which it can reach the external network for internet connectivity.

2016-01-28 13:31:37 -0600 received badge  Famous Question (source)
2015-10-12 00:38:02 -0600 received badge  Supporter (source)
2015-10-12 00:37:56 -0600 answered a question Is there a way to attach a fixed PRIVATE ip to an instance?

Create a neutron port with fixed IP on a specific network,subnet -

neutron port-create --fixed-ip subnet_id=<subnet_id>,ip_address=<fixed_ip> --name flat-port-subnet1 <net_id>

launch the VM with nova command and using '--port-id' to get the above mentioned fixed IP address

2015-09-30 01:54:22 -0600 answered a question flat and vlan network creation shows error-"No tenant network is available for allocation"

try adding --provider:physical_network=physnet2 --provider:network_type=vlan while creating the network

2015-09-30 01:49:56 -0600 received badge  Notable Question (source)
2015-09-30 01:49:56 -0600 received badge  Popular Question (source)
2015-09-02 03:39:56 -0600 asked a question VM connectivity issue between SRIOV ports & virtio ports in Kilo with 82599

Hi All,

I have a Openstack Kilo setup for a customer with SRIOV. There are 2 VMs on a compute node. There are 3 flat networks( flat-sriov-net1 / 60.0.1.x , flat-sriov-net2/60.0.2.x & flat-net/192.168.100.x) defined for this cluster.

The first VM has 3 virtio ports, each from the 3 networks. The second VM(VM_2virtio_1VF) has 1 SRIOV ports(Niantic 10G port) defined on the flat-sriov-net2 and a two normal virtio ports defined on the flat-net & flat-sriov-net1.

I am unable to ping SRIOV port from virtio ports (and vice versa) for the interfaces which are on same flat network (with same subnet). Here is the details of the VM and ports-

VM_2virtio_1VF (1 VF , 2 virtio ports) details -

a) SRIOV Port – mac - fa:16:3e:1b:21:56 , IP - 60.0.2.12

b) Virtio Ports - mac – fa:16:3e:dc:7f:e3 , IP – 60.0.1.13

c) Virtio Ports - mac - fa:16:3e:50:52:93 , IP – 192.168.100.53

VM (3 virtio ports) details –

d) Virtio Ports - mac - fa:16:3e:f0:1c:c4 , IP – 60.0.2.11

e) Virtio Ports - mac - fa:16:3e:90:7e:5c , IP – 60.0.1.11

f) Virtio Ports - mac - fa:16:3e:4b:dc:7b , IP – 192.168.100.51

Communication between a & d is not working (i.e between SRIOV & virtio port).

Communication between b & e and c & f is working (i.e virtio to virtio ).

Please help to find out the cause.

Regards, Vikrant

2014-12-25 02:49:41 -0600 received badge  Popular Question (source)
2014-12-25 02:49:41 -0600 received badge  Famous Question (source)
2014-12-25 02:49:41 -0600 received badge  Notable Question (source)
2014-12-10 01:03:02 -0600 received badge  Enthusiast
2014-11-28 04:11:21 -0600 commented answer 'neutron agent-list' show nothing

what is the neutron version, can you post the o/p of "neutron --version"

2014-11-27 05:29:05 -0600 commented answer Instance failing to spawn, logs show `NovaException: Unexpected vif_type=binding_failed`

Hi,

I am getting this error in Juno release. i am using gre in 3 node setup. Getting error log in nova-compute.log, other logs are fine.

2014-11-26 09:00:38 -0600 commented answer Instance failing to spawn, logs show `NovaException: Unexpected vif_type=binding_failed`

can you share what exactly you added in /etc/init/neutron-server.conf file

2014-06-09 23:58:23 -0600 received badge  Editor (source)
2014-06-09 23:57:37 -0600 asked a question Unable to get neutron metering notification Data for Routers

Hi All,

I have configured neutron metering agent as per the link - https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth (https://wiki.openstack.org/wiki/Neutr...) , I want to collect the Router metering information.

I created metering Label and Rules using the commands "neutron meter-label-create" and "neutron meter-label-rule-create" . But i am not getting the Metering Notification Data in the metering_agent.log file.

Also with the some debugging of the code i found that the function "_get_traffic_counters" in metering_agent.py is not furnishing the traffic counter data.

Unable to get router id in the code rm = self.routers.get(router['rid']) . Please find the code details in the link - https://github.com/openstack/neutron/blob/stable/icehouse/neutron/services/metering/drivers/iptables/iptables_driver.py#L263 (https://github.com/openstack/neutron/...)

Please help.

Regards, Vikrant