Re: [openstack-dev] [ceilometer] When do we import aodh?

2015-06-18 Thread Julien Danjou
On Wed, Jun 17 2015, gordon chung wrote: don't we need an initial migration still? to create all the base tables? You don't need a migration for that, SQLAlchemy handles that on its own. We'll add an initial migration once we start using Alembic. any thought to using ceilometer repo as a

Re: [openstack-dev] [ceilometer] When do we import aodh?

2015-06-17 Thread gordon chung
i've no idea how to add comments to github so i'll ask here. On 16/06/2015 11:12 AM, Julien Danjou wrote: On Tue, Jun 16 2015, Chris Dent wrote: 5. anything in tempest to worry about? Yes, we need to adapt and reenable tempest after. 6. what's that stuff in the ceilometer dir? 6.1.

[openstack-dev] [ceilometer] When do we import aodh?

2015-06-16 Thread Julien Danjou
Hi there, The alarm code split blueprint¹ has been approved, and I finished the split of the code base. It's available online at: https://github.com/jd/aodh tox -e pep8,py27,docs passes. To me the next step is to: 1. Someone cares and review what I've done in the repository 2. import the

Re: [openstack-dev] [ceilometer] When do we import aodh?

2015-06-16 Thread Chris Dent
On Tue, 16 Jun 2015, Julien Danjou wrote: To me the next step is to: 1. Someone cares and review what I've done in the repository 2. import the code into openstack/aodh Assuming that we'll do whatever is required to finish things after moving it under openstack/ then whatever you've done in

Re: [openstack-dev] [ceilometer] When do we import aodh?

2015-06-16 Thread Julien Danjou
On Tue, Jun 16 2015, Chris Dent wrote: 5. anything in tempest to worry about? Yes, we need to adapt and reenable tempest after. 6. what's that stuff in the ceilometer dir? 6.1. Looks like migration artifacts, what about migration in general? That's a rest of one of the many