Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-17 Thread Angus Salkeld
On Fri, Jul 17, 2015 at 8:52 PM, Julien Danjou wrote: > On Thu, Jul 16 2015, Angus Salkeld wrote: > > Hi Angus, > > > I just saw this, and I am concerned this is going to kill Heat's gate > (and > > user's templates). > > > > Will this be hidden within the client so that as long as we have aodh >

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-17 Thread Julien Danjou
On Thu, Jul 16 2015, Angus Salkeld wrote: Hi Angus, > I just saw this, and I am concerned this is going to kill Heat's gate (and > user's templates). > > Will this be hidden within the client so that as long as we have aodh > enabled in our gate's devstack > this will just work? As Gordon said,

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-16 Thread gord chung
On 16/07/2015 12:05 AM, Angus Salkeld wrote: Will this be hidden within the client so that as long as we have aodh enabled in our gate's devstack this will just work? yes, we discussed this last week during our midcycle. the plan going forward is to allow current existing Ceilometer alarm f

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-15 Thread TIANTIAN
I'd agree with Angus. 在 2015-07-16 12:05:25,"Angus Salkeld" 写道: On Tue, Jun 30, 2015 at 6:09 PM, Julien Danjou wrote: On Mon, Jun 29 2015, Ildikó Váncsa wrote: > I think removing options from the API requires version bump. So if we plan to > do this, that should be introduced in v3 as opposed

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-15 Thread Angus Salkeld
On Tue, Jun 30, 2015 at 6:09 PM, Julien Danjou wrote: > On Mon, Jun 29 2015, Ildikó Váncsa wrote: > > > I think removing options from the API requires version bump. So if we > plan to > > do this, that should be introduced in v3 as opposed to v2, which should > remain > > the same and maintained

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-02 Thread gordon chung
al Message- From: gordon chung [mailto:g...@live.ca] Sent: Tuesday, June 30, 2015 3:48 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps On 29/06/2015 11:40 AM, Chris Dent wrote: On Mon, 29 Jun 2015, Julien Danjou wrote:

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-02 Thread gordon chung
al Message- From: gordon chung [mailto:g...@live.ca] Sent: Tuesday, June 30, 2015 3:48 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps On 29/06/2015 11:40 AM, Chris Dent wrote: On Mon, 29 Jun 2015, Julien Danjou wrote:

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-02 Thread Ryota Mibu
t: Tuesday, June 30, 2015 3:48 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps > > > > On 29/06/2015 11:40 AM, Chris Dent wrote: > > On Mon, 29 Jun 2015, Julien Danjou wrote: > > > >

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-01 Thread Eoghan Glynn
> > > I think removing options from the API requires version bump. So if we > > > plan to do this, that should be introduced in v3 as opposed to v2, > > > which should remain the same and maintained for two cycles (assuming > > > that we still have this policy in OpenStack). It this is achievable

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-30 Thread Ildikó Váncsa
Hmm, as it is a change that affects the user, in my opinion it is still an API change. Have we decided about the client, whether the alarming module will have a separate client or we will keep the current ceilometer-client? I guess more the latter one at least as a starting point, I just wanted

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-30 Thread Julien Danjou
On Tue, Jun 30 2015, Ildikó Váncsa wrote: > Will this be accessible in the same way as currently or it needs > changes on client side? You may just need to pass more options to the client to force another endpoint to be used when talking to the alarming part. We could make this change in the clie

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-30 Thread Ildikó Váncsa
> -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: June 30, 2015 10:10 > To: Ildikó Váncsa > Cc: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps &

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-30 Thread Julien Danjou
On Mon, Jun 29 2015, Julien Danjou wrote: FTR today I've copied the members of ceilometer-core to aodh-core. We'll be able to manage to the team independently like we do with Gnocchi, based on who is doing what in the different repositories. > Hi team, > > Aodh has been imported and is now avail

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-30 Thread Julien Danjou
On Mon, Jun 29 2015, Ildikó Váncsa wrote: > I think removing options from the API requires version bump. So if we plan to > do this, that should be introduced in v3 as opposed to v2, which should remain > the same and maintained for two cycles (assuming that we still have this > policy > in OpenS

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-29 Thread Ildikó Váncsa
Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps > > I'm afraid user experience will change because of API. Do we have a plan > about it? > > Will we interact with Aodh through ceilometer-api first? Or mak

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-29 Thread Nadya Shakhat
I'm afraid user experience will change because of API. Do we have a plan about it? Will we interact with Aodh through ceilometer-api first? Or make user to go to aodh-api service? So I agree with Gordon that code-cleanup is more preferred option because we can't maintain two version simultaneously.

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-29 Thread gordon chung
On 29/06/2015 11:40 AM, Chris Dent wrote: On Mon, 29 Jun 2015, Julien Danjou wrote: Hi team, Aodh has been imported and is now available at: https://git.openstack.org/cgit/openstack/aodh/ woot! I'm pretty clear about the next steps for Aodh and what we need to build, but something is s

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-29 Thread Chris Dent
On Mon, 29 Jun 2015, Julien Danjou wrote: Hi team, Aodh has been imported and is now available at: https://git.openstack.org/cgit/openstack/aodh/ woot! I'm pretty clear about the next steps for Aodh and what we need to build, but something is still not clear to me. Do we go ahead and bite

[openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-06-29 Thread Julien Danjou
Hi team, Aodh has been imported and is now available at: https://git.openstack.org/cgit/openstack/aodh/ You should add it to your review list on Gerrit I guess. I'm pretty clear about the next steps for Aodh and what we need to build, but something is still not clear to me. Do we go ahead and