Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[Julien Danjou]

On Mon, Dec 04 2017, gordon chung wrote:

> but at the end of the day, are you building for reality or for some 
> personal ideal scenario? :p

Haha, you know that if I was building for an ideal scenario, most of
Ceilometer would probably have never existed in this way.

Half of Ceilometer is already hacking around OpenStack project
limitation for the last 5 years.

> is there a service that offers a stats endpoint?

Outside of OpenStack? Plenty. :)

-- 
Julien Danjou
/* Free Software hacker
   https://julien.danjou.info */


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[gordon chung]

On 2017-12-04 08:53 AM, Julien Danjou wrote:
> Which is usually a problem because of the APIs, not Ceilometer. They're
> sometimes utterly slow for simple things and other times don't offer a
> way to retrieve what Ceilometer needs in a batch-y way.
> 
>> in general, there's a preference that stats be pushed to ceilometer
>> rather than pulled.
> Yes, but for the wrong reasons. Having a component sending a batch of
> notification every hour without any configuration knob and granularity
> choice is a PITA for the users. Plus it ususally comes from a single
> point (of failure?).

well you can configure it, just at a per service level.. but that's a 
fair point.

> 
> Ceilometer would do a better job than $project at getting this info, if
> said project(s) would offer a proper and performant API to retrieve them
> efficiently.

but at the end of the day, are you building for reality or for some 
personal ideal scenario? :p is there a service that offers a stats endpoint?

-- 
gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[Duncan Thomas]

Either way step one is to propose the code for a better replacement. I
doubt you'll get much opposition to that.

No need to propose removing the old code immediately, it can live in
parallel for as long as needed.

On 4 December 2017 at 15:14, Jaze Lee  wrote:
> 2017-12-04 19:36 GMT+08:00 Duncan Thomas :
>> Why remove something that works and people are using?
>
> Yes, removing it will make noise.
>
>>
>> If polster can be set up to do the job, then great, but there's no
>> rush to remove the existing infrastructure; this is one case where
>> duplication is very, very cheap.
>
> Yes it is too cheap to refuse. But i think it should be not exists there.
>
>>
>> On 4 December 2017 at 10:30, Jaze Lee  wrote:
>>> Hello,
>>>
>>> Right now,we can get volume from central pollester. Then i think
>>> may be we can drop cinder volume usage.
>>>Cinder volume usage, do not like nova usage which is in nova
>>> compute. It is a cmd.  And should put it in cron. This will cause more
>>> work in devops. If ceilometer
>>> pollester can handle it. I think may be we should remove it?
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 谦谦君子
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> --
>> Duncan Thomas
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> 谦谦君子
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Duncan Thomas

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[Jaze Lee]

2017-12-04 19:36 GMT+08:00 Duncan Thomas :
> Why remove something that works and people are using?

Yes, removing it will make noise.

>
> If polster can be set up to do the job, then great, but there's no
> rush to remove the existing infrastructure; this is one case where
> duplication is very, very cheap.

Yes it is too cheap to refuse. But i think it should be not exists there.

>
> On 4 December 2017 at 10:30, Jaze Lee  wrote:
>> Hello,
>>
>> Right now,we can get volume from central pollester. Then i think
>> may be we can drop cinder volume usage.
>>Cinder volume usage, do not like nova usage which is in nova
>> compute. It is a cmd.  And should put it in cron. This will cause more
>> work in devops. If ceilometer
>> pollester can handle it. I think may be we should remove it?
>>
>>
>>
>>
>>
>> --
>> 谦谦君子
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Duncan Thomas
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
谦谦君子

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[Jaze Lee]

2017-12-04 20:57 GMT+08:00 gordon chung :
>
>
> On 2017-12-04 05:30 AM, Jaze Lee wrote:
>>  Right now,we can get volume from central pollester. Then i think
>> may be we can drop cinder volume usage.
>
> which metrics are you referring to? just for the record, except for
> libvirt stats, the polling done by ceilometer is against the API which
> may create additional load.

I mean volume.exists snapshot.exists, and backup.exists

>
> in general, there's a preference that stats be pushed to ceilometer
> rather than pulled.

The cinder volume usage cmd is too difficult to use in production. I
do not know
why don't learn from nova?  Put it in a periodic task, and can be configurable.


>
> cheers,
>
> --
> gord
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
谦谦君子

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[Julien Danjou]

On Mon, Dec 04 2017, gordon chung wrote:

> On 2017-12-04 05:30 AM, Jaze Lee wrote:
>>  Right now,we can get volume from central pollester. Then i think
>> may be we can drop cinder volume usage.
>
> which metrics are you referring to? just for the record, except for 
> libvirt stats, the polling done by ceilometer is against the API which 
> may create additional load.

Which is usually a problem because of the APIs, not Ceilometer. They're
sometimes utterly slow for simple things and other times don't offer a
way to retrieve what Ceilometer needs in a batch-y way.

> in general, there's a preference that stats be pushed to ceilometer 
> rather than pulled.

Yes, but for the wrong reasons. Having a component sending a batch of
notification every hour without any configuration knob and granularity
choice is a PITA for the users. Plus it ususally comes from a single
point (of failure?).

Ceilometer would do a better job than $project at getting this info, if
said project(s) would offer a proper and performant API to retrieve them
efficiently.

-- 
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[gordon chung]

On 2017-12-04 05:30 AM, Jaze Lee wrote:
>  Right now,we can get volume from central pollester. Then i think
> may be we can drop cinder volume usage.

which metrics are you referring to? just for the record, except for 
libvirt stats, the polling done by ceilometer is against the API which 
may create additional load.

in general, there's a preference that stats be pushed to ceilometer 
rather than pulled.

cheers,

-- 
gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer][cinder]about cinder volume usage

[Duncan Thomas]

Why remove something that works and people are using?

If polster can be set up to do the job, then great, but there's no
rush to remove the existing infrastructure; this is one case where
duplication is very, very cheap.

On 4 December 2017 at 10:30, Jaze Lee  wrote:
> Hello,
>
> Right now,we can get volume from central pollester. Then i think
> may be we can drop cinder volume usage.
>Cinder volume usage, do not like nova usage which is in nova
> compute. It is a cmd.  And should put it in cron. This will cause more
> work in devops. If ceilometer
> pollester can handle it. I think may be we should remove it?
>
>
>
>
>
> --
> 谦谦君子
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Duncan Thomas

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev