Re: [openstack-dev] [Blazar] Anyone interested?

Yes, Blazar is a really interesting project. I worked on it some time ago and I really enjoy it. Sadly my obligations at work don't let me to still working on it, but I', happy that there still some interest in Blazar. Pablo. On 31/08/15 09:19, Zhenyu Zheng wrote: Hello, It seems like an

[openstack-dev] [blazar] py26 and py27 jobs failing

Blazar cores, Please review https://review.openstack.org/99389. We need this merged ASAP in order to get a +1 from Jenkins in our py26 and py27 jobs. Pecan new version returns a 204 instead 200 in one case (when the API returns and empty dictionary) and one test case is failing for this

[openstack-dev] [Blazar] June 27 Weekly meeting

I have an All Hands this noon, so I could attend only to the first half of Blazar meeting. Pablo. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [blazar] Blazar client V2 REST API support and Horizon integration

Blazar cores, I managed to get our client working against our V2 REST API and I implemented the first bits of our Blazar Dashboard for Horizon. In order to continue working on the last, I need this patches on master. I suggest this order: https://review.openstack.org/#/c/99389/ (V2

[openstack-dev] [blazar] Blazar Nova renaming patches

I finished the Blazar-Nova renaming. The only thing left is to update oslo with the new name, but I'll do that when the rename patches land to master. So, cores please give your blessing to this patches: https://review.openstack.org/98496, https://review.openstack.org/100914,

[openstack-dev] [blazar] trust_id critical bug

Blazar cores, Please check https://review.openstack.org/#/c/102004/ It fixes https://launchpad.net/bugs/1333413 I found the bug using our tempest test suite ;) (I'm trying to get that tempest suite as a gate job) Thanks. Pablo.

[openstack-dev] [Blazar] June 20 Weekly meeting

Tomorrow is a holiday in Argentina, so I won't be able to attend to the meeting. Pablo. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Climate] Today's weekly meeting

Hi all, We will have the meeting today? Pablo. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] reservation of fixed ip

Hi, I'm part of a project that aims to manage Reservations on OpenStack. Maybe this could be implemented on it. The name of the project is Blazar (ex Climate). Currently we have two reservation plugins: one for physical host reservations and other for virtual instances reservation. We are

Re: [openstack-dev] [Climate] Query leases by project_id/domain_id

Any comments on this? On Mon, 2014-04-28 at 16:57 +, Fuente, Pablo A wrote: Any comments on this? On Tue, 2014-04-22 at 18:58 +, Fuente, Pablo A wrote: Hi I'm trying to tackle this bug (https://bugs.launchpad.net/climate/+bug/1304435). The options that I'm considering

Re: [openstack-dev] [climate] Friday Meeting

+1 I can't attend to the metting too, I will be at the marriage of a friend. BTW, I will like to tell you guys, that for us (Argentina folks), today and tomorrow are days off. On Thu, 2014-05-01 at 00:11 +0400, Dina Belova wrote: +1 On Wed, Apr 30, 2014 at 11:41 PM, Sylvain Bauza

[openstack-dev] [climate] Client and REST API versioning

Hi, We recently implemented our V2 REST API, and at this moment we are trying to get working our python client against this new version. For this reason, we start a discussion about how the client will choose/set the REST API version to use. BTW, we are not deprecating our V1 REST API, so

Re: [openstack-dev] [Climate] Query leases by project_id/domain_id

Any comments on this? On Tue, 2014-04-22 at 18:58 +, Fuente, Pablo A wrote: Hi I'm trying to tackle this bug (https://bugs.launchpad.net/climate/+bug/1304435). The options that I'm considering are: 1 - Add the project_id query parameter to the leases API 2 - Use

Re: [openstack-dev] [Climate] nominating Pablo Andres Fuente for the Climate core reviewers team

: dark_harlequine1 2014-04-24 17:43 GMT+04:00 Fuente, Pablo A pablo.a.fue...@intel.com: Thanks, it's an honor! On Thu, 2014-04-24 at 13:20 +, Sanchez, Cristian A wrote: Congratulations Pablo! From: Sylvain Bauza sylvain.ba

Re: [openstack-dev] [Climate] nominating Pablo Andres Fuente for the Climate core reviewers team

Thanks, it's an honor! On Thu, 2014-04-24 at 13:20 +, Sanchez, Cristian A wrote: Congratulations Pablo! From: Sylvain Bauza sylvain.ba...@gmail.commailto:sylvain.ba...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Climate] Query leases by project_id/domain_id

Hi I'm trying to tackle this bug (https://bugs.launchpad.net/climate/+bug/1304435). The options that I'm considering are: 1 - Add the project_id query parameter to the leases API 2 - Use the X_PROJECT_ID header I prefer the first option, but I would like to know

[openstack-dev] [Heat] Version Negotiation Middleware Accept Header issue

Hi, I noticed that the Accept HTTP Header checked in the Version Negotiation Middleware by Heat is the same MIME type used by Glance (application/vnd.openstack.images-) Is this OK, or should it be something like application/vnd.openstack.orchestration-? If this is the case