n through
Heat
>
>On Thu, Nov 14, 2013 at 08:22:57AM +0000, Kodam, Vijayakumar (EXT-Tata
Consultancy Ser - FI/Espoo) wrote:
>
>> Thanks Steve Baker for the information. I am also waiting to hear from
Steve Hardy, if keystone trust system will fix the nova flavors admin
p
Hi,
Currently there is no way to enable or disable meters without restarting
ceilometer.
There are cases where operators do not want to run all the meters continuously.
In these cases, there should be a way to disable or enable them dynamically.
We are working on this feature right now. I have
>-Original Message-
>From: ext Julien Danjou [mailto:jul...@danjou.info]
>Subject: Re: [openstack-dev] [Ceilometer] Dynamic Meters in Ceilometer
>
>On Tue, Dec 31 2013, Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo)
>wrote:
>
>Hi,
>
>> Curre
From: ext Chmouel Boudjnah [mailto:chmo...@enovance.com]
Sent: Monday, January 06, 2014 2:19 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ceilometer] Dynamic Meters in Ceilometer
On Mon, Jan 6, 2014 at 12:52 PM, Kodam, Vijayakumar (EXT-Tata
per-project settings should be implemented for all the
meters/resources/APIs in ceilometer and should be handled by a different
blueprint.
Regards,
VijayKumar
>> -Original Message-
>> From: Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo)
>> [mailto:vijayakumar.k
From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
Sent: 06 January 2014 23:35
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ceilometer] Dynamic Meters in Ceilometer
On Tue, Dec 31, 2013 at 4:53 AM, Kodam, Vijayakumar (EXT-Tata Consultancy
tors to push configuration changes out to multiple targets using
> puppet/chef/etc. and have the daemons pick it up without restart.
> Thumbs up to that.
>
>As Tim Bell suggested, API-based enabling/disabling would allow users to
> update meters via script, but then there's th
multiple targets using
> puppet/chef/etc. and have the daemons pick it up without restart.
> Thumbs up to that.
>
>As Tim Bell suggested, API-based enabling/disabling would allow users to
> update meters via script, but then there's the question of how to work out
> t
Hi,
Updated the blueprint based on the suggestions from the community.
Mentioned high level call-flow.
Please go through it and let me know your views.
https://blueprints.launchpad.net/ceilometer/+spec/dynamic-meters
Regards,
VijayKumar Kodam
___
Hi,
In Telecom Cloud applications, the requirements for every application are
different. One application might need 10 CPUs, 10GB RAM and no disk. Another
application might need 1 CPU, 512MB RAM and 100GB Disk. This varied
requirements directly affects the flavors which need to be created for
>-Original Message-
>From: Clint Byrum [mailto:cl...@fewbar.com]
>Sent: Tuesday, November 12, 2013 9:24 PM
>To: openstack-dev
>Subject: Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat
>
>Excerpts from Kodam, Vijayakumar (EXT-Tata Consulta
0 AM, Steven Dake wrote:
>>On 11/12/2013 10:25 AM, Kodam, Vijayakumar (EXT-Tata Consultancy Ser -
FI/Espoo) wrote:
>>Hi,
>>
>> In Telecom Cloud applications, the requirements for every
application are different. One application might need 10 CPUs,
>not the video I was looking for, but he kind of makes the point about
>planning...
>http://youtu.be/2E0C9zLSINE?t=42m55s
>
># Shawn Hartsock
>
Thanks Shawn for your inputs. As I have mentioned earlier, the usecase is
mostly for telecom cloud applications running in our private cloud.
The hardw
13 matches
Mail list logo
