Re: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core

2014-02-10 Thread Jason Dunsmore
Thanks everyone. It's an honor to join the team. I'm looking forward to meeting you all in Atlanta. On Mon, Feb 10 2014, Jeff Peeler wrote: On Mon, Feb 10, 2014 at 11:38:40AM +1300, Steve Baker wrote: I would like to nominate Jason Dunsmore for heat-core. His reviews are valuable

Re: [openstack-dev] testr help

2014-03-12 Thread Jason Dunsmore
On Wed, Mar 12 2014, John Dennis wrote: On 03/12/2014 01:22 PM, Zane Bitter wrote: On 10/03/14 20:29, Robert Collins wrote: Which bits look raw? It should only show text/* attachments, non-text should be named but not dumped. I was thinking of the: pythonlogging:'': {{{ part. Yes,

Re: [openstack-dev] [Heat] Resource dependencies

2014-03-21 Thread Jason Dunsmore
This is what you're looking for: http://docs.openstack.org/developer/heat/glossary.html#term-dependency On Thu, Mar 20 2014, Shaunak Kashyap wrote: Hi, In a Heat template, what does it mean for a resource to depend on another resource? As in, what is the impact of creating a dependency? I

Re: [openstack-dev] User mailing lists for OpenStack projects

2014-03-21 Thread Jason Dunsmore
Here is the mailing list for openstack usage questions (for all projects): http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack On Thu, Mar 20 2014, Shaunak Kashyap wrote: Hi folks, I am relatively new to OpenStack development as one of the developers on the unified PHP SDK for

Re: [openstack-dev] [Solum/Heat] Is Solum really necessary?

2013-11-15 Thread Jason Dunsmore
Great description of Heat vs. Solum! This belongs in the FAQs of both projects IMO. This question is bound to keep coming up (for good reason). On Thu, Nov 14 2013, Angus Salkeld wrote: On 14/11/13 13:41 -0500, Jay Pipes wrote: So while I have been on vacation, I've been thinking about Solum

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Jason Dunsmore
On Wed, Nov 27 2013, Zane Bitter wrote: Parameters: db_name: group: db order: 0 db_username: group: db order: 1 db_password: group: db

Re: [openstack-dev] [all][specs] Please stop doing specs for any changes in projects

2014-07-01 Thread Jason Dunsmore
On Mon, Jun 30 2014, Joshua Harlow wrote: There is a balance here that needs to be worked out and I've seen specs start to turn into requirements for every single patch (even if the patch is pretty small). I hope we can rework the 'balance in the force' to avoid being so strict that every

Re: [openstack-dev] [all][specs] Please stop doing specs for any changes in projects

2014-07-01 Thread Jason Dunsmore
additional effort. On Tue, Jul 1, 2014 at 10:30 AM, Jason Dunsmore jason.dunsm...@rackspace.com wrote: On Mon, Jun 30 2014, Joshua Harlow wrote: There is a balance here that needs to be worked out and I've seen specs start to turn into requirements for every single patch (even

Re: [openstack-dev] [Heat] Proposing Thomas Spatzier for heat-core

2014-04-22 Thread Jason Dunsmore
+1 On Tue, Apr 22 2014, Steven Dake wrote: HOT seemed like a job for Ethan Hunt. Nice work on finishing the job! big +1 from me On 04/22/2014 11:43 AM, Zane Bitter wrote: Resending with [Heat] in the subject line. My bad. On 22/04/14 14:21, Zane Bitter wrote: I'd like to propose

Re: [openstack-dev] [heat] [neutron] [trove] [swift] Uniform name for logger in projects

2014-05-22 Thread Jason Dunsmore
(Adding relevant projects to subject. Hope I didn't miss any.) Heat, Neutron, Trove, and Swift devs, Do we want to change all instances of logger variable names to LOG (like most OpenStack projects use) and enforce that via the hacking rules? Regards, Jason On Wed, May 21 2014, Sergey

Re: [openstack-dev] [Heat] Nominating Pavlo Shchelokovskyy for heat-core

2014-10-07 Thread Jason Dunsmore
+1! On Mon, Oct 06 2014, Zane Bitter wrote: I'd like to propose that we add Pavlo Shchelokovskyy to the heat-core team. Pavlo has been a consistently active member of the Heat community - he's a regular participant in IRC and at meetings, has been making plenty of good commits[1] and

[openstack-dev] [Heat] Multi-engine design feedback requested

2013-08-29 Thread Jason Dunsmore
Heat devs, Liang pointed out a race-condition in the current multi-engine implementation that will be difficult to fix without a DB lock. I've discussed the multi-engine design with my teammates and written up a few alternative designs here: https://etherpad.openstack.org/vJKcZcQOU9 Every

Re: [openstack-dev] [Heat] Multi-engine design feedback requested

2013-08-30 Thread Jason Dunsmore
Heat devs, There's been some good discussion on the Etherpad: https://etherpad.openstack.org/vJKcZcQOU9 I've added a Votes section under alternate options 1-5. Please read over the discussion and add your vote. Thanks, Jason On Thu, Aug 29 2013, Jason Dunsmore wrote: Heat devs, Liang

Re: [openstack-dev] [Heat] core team changes

2015-01-28 Thread Jason Dunsmore
+1 On Tue, Jan 27 2015, Angus Salkeld wrote: Hi all After having a look at the stats: http://stackalytics.com/report/contribution/heat-group/90 http://stackalytics.com/?module=heat-groupmetric=person-day I'd like to propose the following changes to the Heat core team: Add: Qiming Teng

Re: [openstack-dev] [Heat] core team nomination

2015-10-20 Thread Jason Dunsmore
+1! From: Sergey Kraynev Sent: Tuesday, October 20, 2015 8:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Heat] core team nomination I'd like to propose new candidates for heat

Re: [openstack-dev] [heat] Unable to launch nova instance with the new flavor

2016-03-14 Thread Jason Dunsmore
Hi Bharath, It sounds like you've hit this bug https://bugs.launchpad.net/heat/+bug/1556317 A fix is in progress https://review.openstack.org/#/c/291971/? Regards, Jason From: bharath thiruveedula Sent: Monday, March 14, 2016 1:12

Re: [openstack-dev] [heat] update_allowed vs. immutable

2016-05-02 Thread Jason Dunsmore
Hi Praveen, The docs you referred to in the plugin guide is for the resource property attributes - they have nothing to do with parameters. This is an important distinction because there is also an "immutable" parameter attribute. The "immutable" property attribute was added because an