abhishek-talwar's profile - activity

2017-04-26 05:08:04 -0500 received badge  Famous Question (source)
2017-04-26 05:08:04 -0500 received badge  Notable Question (source)
2016-12-18 12:14:02 -0500 received badge  Famous Question (source)
2016-12-18 12:14:02 -0500 received badge  Notable Question (source)
2016-09-19 09:14:22 -0500 received badge  Notable Question (source)
2016-09-19 09:14:22 -0500 received badge  Famous Question (source)
2016-08-30 12:28:04 -0500 received badge  Famous Question (source)
2016-07-17 07:24:22 -0500 received badge  Popular Question (source)
2016-01-12 13:10:50 -0500 received badge  Famous Question (source)
2016-01-02 22:06:28 -0500 received badge  Notable Question (source)
2016-01-01 05:20:58 -0500 received badge  Popular Question (source)
2015-12-31 22:19:50 -0500 received badge  Popular Question (source)
2015-12-30 23:38:22 -0500 asked a question Calculate VM processes running on hosts ?

Hi Folks,

Does OpenStack kilo provide us a way to calculate the "VM PROCESSES" running on a host or a VM ??

If there are capabilities do we have any existing command that can help me.

2015-12-30 23:36:35 -0500 asked a question Calculate cpu utilization of a complete host ?

Hi Folks,

I currently working on OpenStack kilo and was looking for a way that can help us to calculate "the CPU utilization of a host and not a VM".

ceilometer sample-list helps us to calculate the cpu_util for a VM but not for a host. So if there any command or way that can be used for this purpose.

2015-12-11 14:50:02 -0500 received badge  Notable Question (source)
2015-12-07 04:43:48 -0500 asked a question Can mistral help me in informing where a task failed and why it failed ?

As Mistral can help us in scheduling taks in OpenStack. So can it also help us with that if a Task failed why did it failed and at which postion it failed ?

So this can help the user as he can start from the point it failed last time and doesnt has to start from all over again.

2015-11-28 02:43:00 -0500 received badge  Famous Question (source)
2015-11-15 20:31:05 -0500 received badge  Famous Question (source)
2015-10-29 05:35:26 -0500 received badge  Famous Question (source)
2015-09-23 01:34:52 -0500 received badge  Popular Question (source)
2015-09-23 00:56:37 -0500 commented answer Vcpu allocation to instances

Hi Mathias ,

Thanks a lot for the reply. I still have some doubts : 1. When you say "A VM with 2 vCPUs has access to and uses 2 vCPUs at all times." does that mean that the alloted Vcpus and used Vcpus are same all the time. If a VM has been given 2 Vcpus are both used together all the time.

2015-09-22 08:38:01 -0500 received badge  Notable Question (source)
2015-09-22 04:58:50 -0500 asked a question Vcpu allocation to instances

Hi Folks,

I have a doubt regarding Vcpu that are assigned to an instance in OpenStack.

When we say that we are assigning 5 Vcpus to an instance, does that mean that the instance will be using all those 5 vcpus together or it is on the load on it.

So the question is are the Vcpus consecutively used or it is used one by one.

Also if they are used one by one how can we get to know how many Vcpus is the VM currently using.

2015-09-22 00:06:26 -0500 commented answer vcpu usage of an instance ?

Hi Omar,

I am not looking at the CPU utilization. Basically what I want is the count of Vcpus that are currently used. For example : a number like 2 or 3 if an instance is assigned 5 Vcpus and it is using 2 or 3 currently.

2015-09-22 00:04:36 -0500 received badge  Popular Question (source)
2015-09-21 06:01:20 -0500 asked a question vcpu usage of an instance ?

The "Vcpu" meter in the ceilometer meter-list tells you about the number of Vcpu's assigned to that instance. How can we find the number of Vcpu's the instance is using at the moment.

For example: If I create an instance and assign it 5 Vcpu's how can I check the number of Vcpus the instance is using at the moment.

Kindly provide some information on this.

2015-09-16 20:55:54 -0500 received badge  Notable Question (source)
2015-09-16 13:52:53 -0500 received badge  Popular Question (source)
2015-09-16 08:19:36 -0500 received badge  Notable Question (source)
2015-09-16 08:19:36 -0500 received badge  Popular Question (source)
2015-09-16 06:47:53 -0500 asked a question how can we get how many vcups an instance is using from its assigned number of vcpus ?

I have a kilo multinode OpenStack setup. I have a doubt regarding the vcpus usage of an instance.

Supposively I create an instance and assign it 2 vcpus. How can I check that how many vcpus is an instance using ?

2015-09-16 05:20:50 -0500 asked a question how to get memory usage of an instance

I have an OpenStack kilo setup and I am trying to get the memory usage of the instances created in it.

I researched and found that ceilometer has a meter called "memory.usage" that can give us the memory utilization of an instance. However, on doing ceilometer meter-list it does not list "memory.usage" as a meter. After searching I found that this problem is being faced by many contributors and a possible solution is changing nova configurations that does not help.

So can you help me with some other possible solution that can help me in finding an instance's current memory utilization. I am working with something that would require getting the memory and disk utilization.

Please provide a solution for this.

Thanks and Regards

2015-09-16 02:16:30 -0500 received badge  Famous Question (source)
2015-09-11 06:24:18 -0500 received badge  Popular Question (source)
2015-09-10 05:52:22 -0500 asked a question How does an instance with flavor m1.nano (disk = 0, RAM =64) has disk.usage >0 ?

I have installed devstack kilo version of OpenStack and created an instance on it with flavor “m1.nano” that gives a disk of 0 to your instance.

But while checking disk usage of the instance using “disk.usage” meter it gives the output to be greater than 0 so how is it possible ?

**stack@abhishek:/opt/stack/ceilometer$ nova show e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa**
+--------------------------------------+----------------------------------------------------------------+
| Property                             | Value                                                          |
+--------------------------------------+----------------------------------------------------------------+
| OS-DCF:diskConfig                    | AUTO                                                           |
| OS-EXT-AZ:availability_zone          | nova                                                           |
| OS-EXT-SRV-ATTR:host                 | tcs-HP-Compaq-Elite-8300-SFF                                   |
| OS-EXT-SRV-ATTR:hypervisor_hostname  | tcs-HP-Compaq-Elite-8300-SFF                                   |
| OS-EXT-SRV-ATTR:instance_name        | instance-00000002                                              |
| OS-EXT-STS:power_state               | 1                                                              |
| OS-EXT-STS:task_state                | -                                                              |
| OS-EXT-STS:vm_state                  | active                                                         |
| OS-SRV-USG:launched_at               | 2015-09-10T05:24:19.000000                                     |
| OS-SRV-USG:terminated_at             | -                                                              |
| accessIPv4                           |                                                                |
| accessIPv6                           |                                                                |
| config_drive                         | True                                                           |
| created                              | 2015-09-10T05:24:10Z                                           |
| flavor                               | m1.nano (42)                                                   |
| hostId                               | 4a3e03e0a89fbf3790a1b1cd59b1b10acbaad6aa31a4361996d52440       |
| id                                   | e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa                           |
| image                                | cirros-0.3.2-x86_64-uec (221c46b3-9619-485e-8f60-0e1a363fc0e5) |
| key_name                             | -                                                              |
| metadata                             | {}                                                             |
| name                                 | vmssasa                                                        |
| os-extended-volumes:volumes_attached | []                                                             |
| progress                             | 0                                                              |
| public network                       | 172.24.4.4                                                     |
| security_groups                      | default                                                        |
| status                               | ACTIVE                                                         |
| tenant_id                            | 5f4f5ee531a441d7bb3830529e611c7d                               |
| updated                              | 2015-09-10T05:24:19Z                                           |
| user_id                              | d04b218204414a1891646735befd449c                               |
+--------------------------------------+----------------------------------------------------------------+

**stack@abhishek:/opt/stack/ceilometer$ nova flavor-show m1.nano**
+----------------------------+---------+
| Property                   | Value   |
+----------------------------+---------+
| OS-FLV-DISABLED:disabled   | False   |
| OS-FLV-EXT-DATA:ephemeral  | 0       |
| disk                       | 0       |
| extra_specs                | {}      |
| id                         | 42      |
| name                       | m1.nano |
| os-flavor-access:is_public | True    |
| ram                        | 64      |
| rxtx_factor                | 1.0     |
| swap                       |         |
| vcpus                      | 1       |
+----------------------------+---------+

**stack@abhishek:/opt/stack/ceilometer$ ceilometer sample-list -m 'cpu_util' -q "resource_id=e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa"**
+--------------------------------------+------------+-------+------------+------+---------------------+
| Resource ID                          | Name       | Type  | Volume     | Unit | Timestamp           |
+--------------------------------------+------------+-------+------------+------+---------------------+
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T10:30:54 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T10:20:54 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T10:10:54 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T10:00:54 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T09:48:25 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T09:38:25 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T09:21:42 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T09:11:42 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T09:01:42 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T08:51:42 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T08:41:42 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T08:31:42 |
| e3fd6b56-25df-4498-aa9d-8d9af3dfb4fa | disk.usage | gauge | 11112448.0 | B    | 2015-09-10T08:21:42 |


+--------------------------------------+------------+-------+------------+------+---------------------+
2015-09-09 05:07:49 -0500 answered a question How can I get memory.usage in Ceilometer?

HI Maestropandy,

We are looking to get the memory usage of an instance with this meter. But after installing openstack we dont have memory.usage or disk.usage parameters in the meter-list.

We needed some help in regards in how can we have these meters into our list too.

2015-09-08 01:02:28 -0500 asked a question No memory and disk usage meters from ceilometer

Hi Folks,

I have installed a kilo devstack setup install and I am trying to get the memory and disk usage for my VM's. But on checking the "ceilometer meter-list" I can't find memory.usage or disk.usage meters.

I am searched a lot for this and still couldn't find a solution. So how to enable these meters to our meter-list.

I want all these meters in the ceilometer meter-list so that I can use them to monitor my instances.

Currently the output of ceilometer meter-list is as follows:

+--------------------------+------------+----------------------------------------------+----------------------------------+----------------------------------+
| Name                     | Type       | Resource ID                                  | User ID                          | Project ID                       |
+--------------------------+------------+----------------------------------------------+----------------------------------+----------------------------------+
| cpu                      | cumulative | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| cpu_util                 | gauge      | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| disk.read.bytes          | cumulative | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| disk.read.requests       | cumulative | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| disk.write.bytes         | cumulative | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| disk.write.requests      | cumulative | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| image                    | gauge      | 55a0a2c2-8cfb-4882-ad05-01d7c821b1de         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image                    | gauge      | acd6beef-13e6-4d64-a83d-9e96beac26ef         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image                    | gauge      | ecefcd31-ae47-4079-bd19-efe07f4c33d3         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image.download           | delta      | 55a0a2c2-8cfb-4882-ad05-01d7c821b1de         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image.serve              | delta      | 55a0a2c2-8cfb-4882-ad05-01d7c821b1de         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image.size               | gauge      | 55a0a2c2-8cfb-4882-ad05-01d7c821b1de         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image.size               | gauge      | acd6beef-13e6-4d64-a83d-9e96beac26ef         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image.size               | gauge      | ecefcd31-ae47-4079-bd19-efe07f4c33d3         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image.update             | delta      | 55a0a2c2-8cfb-4882-ad05-01d7c821b1de         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| image.upload             | delta      | 55a0a2c2-8cfb-4882-ad05-01d7c821b1de         |                                  | 22f22fb60bf8496cb60e8498d93d56e8 |
| instance                 | gauge      | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| instance:m1.small        | gauge      | 5314c72b-a2b4-4b2b-bcb1-4057c3d96f77         | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| network.incoming.bytes   | cumulative | nova-instance-instance-00000022-fa163e3bd74e | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| network.incoming.packets | cumulative | nova-instance-instance-00000022-fa163e3bd74e | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| network.outgoing.bytes   | cumulative | nova-instance-instance-00000022-fa163e3bd74e | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
| network.outgoing.packets | cumulative | nova-instance-instance-00000022-fa163e3bd74e | 92876a1aad3c477398137b702a8467d3 | 22f22fb60bf8496cb60e8498d93d56e8 |
+--------------------------+------------+
2015-09-03 08:14:51 -0500 received badge  Famous Question (source)
2015-09-03 08:14:51 -0500 received badge  Notable Question (source)
2015-08-21 14:29:27 -0500 received badge  Famous Question (source)
2015-08-21 14:29:17 -0500 received badge  Famous Question (source)
2015-08-20 14:34:44 -0500 received badge  Famous Question (source)
2015-08-20 14:34:44 -0500 received badge  Popular Question (source)
2015-08-20 14:34:44 -0500 received badge  Notable Question (source)
2015-08-19 12:46:17 -0500 received badge  Popular Question (source)
2015-08-19 12:46:17 -0500 received badge  Notable Question (source)
2015-08-18 23:35:45 -0500 received badge  Famous Question (source)
2015-08-18 09:22:09 -0500 received badge  Famous Question (source)
2015-08-18 01:44:35 -0500 commented answer Ceilometer meter-list is empty (Kilo, CentOS7)

Hi Capsali,

I am having the same issue "The service catalog is empty." Upgraded the ceilometerclient and now the version is 1.4.0 Running the command gives another error "('Connection aborted.' , error(111,'connection refused'))" Kindly suggest on what should be done to solve this issue.