Re: [openstack-dev] [heat] Heat API v2 - Removal of template_url?

On 05/12/13 17:00 +, Steven Hardy wrote: On Thu, Dec 05, 2013 at 04:11:37PM +, ELISHA, Moshe (Moshe) wrote: Hey, I really liked the v2 Heat API (as proposed in Create a new v2 Heat API) and I think it makes a lot of sense. One of the

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

On 26/11/13 22:55 +, Tim Schnell wrote: On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell mailto:tim.schn...@rackspace.com>> wrote: From: Christopher Armstrong mailto:chris.armstr...@rackspace.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev

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

On 19/11/13 19:40 +, Fuente, Pablo A wrote: 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.op

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 18/11/13 12:57 +0100, Zane Bitter wrote: On 16/11/13 11:15, Angus Salkeld wrote: On 15/11/13 08:46 -0600, Christopher Armstrong wrote: On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter wrote: On 15/11/13 02:48, Christopher Armstrong wrote: On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 15/11/13 08:46 -0600, Christopher Armstrong wrote: On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter wrote: On 15/11/13 02:48, Christopher Armstrong wrote: On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld mailto:asalk...@redhat.com>> wrote: On 14/11/13 10:19 -0600, Christopher Arm

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 15/11/13 16:32 +0100, Zane Bitter wrote: On 14/11/13 19:53, Christopher Armstrong wrote: Thanks for the comments, Zane. On Thu, Nov 14, 2013 at 9:56 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: A few comments... #1 thing is that the launch configuration needs to be somehow r

Re: [openstack-dev] Split of the openstack-dev list

On 14/11/13 11:46 -0800, Clint Byrum wrote: Excerpts from Thierry Carrez's message of 2013-11-14 05:12:55 -0800: Hi everyone, I think that we have recently reached critical mass for the openstack-dev mailing-list, with 2267 messages posted in October, and November well on its way to pass 2000 a

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

On 14/11/13 13:41 -0500, Jay Pipes wrote: So while I have been on vacation, I've been thinking about Solum and Heat. And I have some lingering questions in my mind that make me question whether a new server project is actually necessary at all, and whether we really should just be targeting in

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On 14/11/13 10:19 -0600, Christopher Armstrong wrote: http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and provides schemas for inputs and outputs using JSON-S

Re: [openstack-dev] [Solum] Command Line Interface for Solum

On 14/11/13 13:32 +0530, Noorul Islam Kamal Malmiyoda wrote: On Nov 14, 2013 1:10 PM, "Adrian Otto" wrote: Noorul, On Nov 13, 2013, at 7:43 PM, Noorul Islam K M wrote: > Doug Hellmann writes: > >> On Sun, Nov 10, 2013 at 10:15 AM, Noorul Islam K M > >>> >>> Hello all, >>> >>> I registered

Re: [openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

On 12/11/13 15:13 -0800, Christopher Armstrong wrote: Given the recent discussion of scheduled autoscaling at the summit session on autoscaling, I looked into the state of scheduling-as-a-service in and around OpenStack. I found two relevant wiki pages: https://wiki.openstack.org/wiki/EventSched

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

On 12/11/13 10:32 -0800, Clint Byrum wrote: Excerpts from Thomas Spatzier's message of 2013-11-11 08:57:58 -0800: Hi all, I have just posted the following wiki page to reflect a refined proposal for HOT software configuration based on discussions at the design summit last week. Angus also put

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

On 12/11/13 21:49 +, Mark McLoughlin wrote: On Tue, 2013-11-12 at 16:42 -0500, Chuck Short wrote: Hi On Tue, Nov 12, 2013 at 4:24 PM, Mark McLoughlin wrote: On Tue, 2013-11-12 at 13:11 -0800, Shawn Hartsock wrote: > Maybe we should have some 60% rule... that is: If you ch

Re: [openstack-dev] [Mistral] really simple workflow for Heat configuration tasks

and there are not two workflows fighting for control. I do agree that there should just be one. I think once Mistral is more mature we can decide whether to pass full workflow control over to it, but for now the task functionality is all we need. (and a time based one would be neat too btw). -Ang

[openstack-dev] [Mistral] really simple workflow for Heat configuration tasks

Hi all I think some of you were at the Software Config session at summit, but I'll link the ideas that were discussed: https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config-WIP https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config To me the basics of it are: 1. we nee

Re: [openstack-dev] [Solum] Choice of API infrastructure

On 03/11/13 11:26 +0800, Russell Bryant wrote: On 11/02/2013 11:54 AM, Adrian Otto wrote: Noorul, I agree that key decisions should be tracked in blueprints. This is the one for this decision which was made in our 2013-10-18 public meeting. Jay's submission is consistent with the direction indi

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

On 30/10/13 15:27 -0400, Jay Pipes wrote: Has anyone looked into using concoord for distributed locking? https://pypi.python.org/pypi/concoord Looks interesting! -Angus Best, -jay On 10/30/2013 02:39 PM, Joshua Harlow wrote: So my idea here was that to break the abstraction for heat into

Re: [openstack-dev] [Heat] HOT Software configuration proposal

On 28/10/13 16:26 -0700, Clint Byrum wrote: [snip] > My components proposals had no hosted_on, but I've been thinking about the implications of implementing software configuration as resources, and one of the natural consequences might be that hosted_on is the best way of establishing the relat

Re: [openstack-dev] [TripleO][Nova][neutron][Heat][Oslo][Ceilometer][Havana]Single Subscription Point for event notification

On 28/10/13 22:30 +, Qing He wrote: All, I found multiple places/components you can get event alarms, e.g., Heat, Ceilometer, Oslo, Nova etc, notification. But I fail to find any documents as to how to do it in the respective component documents. I 'm wondering if there is document as to

Re: [openstack-dev] [heat] Proposal for new heat-core member

On 25/10/13 12:12 -0700, Steven Dake wrote: Hi, I would like to propose Randall Burt for Heat Core. He has shown interest in Heat by participating in IRC and providing high quality reviews. The most important aspect in my mind of joining Heat Core is output and quality of reviews. Randall

Re: [openstack-dev] [Heat] HOT Software configuration proposal

On 25/10/13 09:25 -0700, Clint Byrum wrote: Excerpts from Angus Salkeld's message of 2013-10-24 18:48:16 -0700: On 24/10/13 11:54 +0200, Patrick Petit wrote: >Hi Clint, >Thank you! I have few replies/questions in-line. >Cheers >Patrick >On 10/23/13 8:36 PM, Clint Byrum wrote: >>I think this fits

Re: [openstack-dev] [Heat] HOT Software configuration proposal

On 24/10/13 11:54 +0200, Patrick Petit wrote: Hi Clint, Thank you! I have few replies/questions in-line. Cheers, Patrick On 10/23/13 8:36 PM, Clint Byrum wrote: Excerpts from Patrick Petit's message of 2013-10-23 10:58:22 -0700: Dear Steve and All, If I may add up on this already busy thread t

Re: [openstack-dev] [Heat] Incorporate Auditing Support / Usage Notifications

On 21/10/13 15:11 -1000, Angus Salkeld wrote: Hi all There has been some interest in Heat generating usage notifications http://summit.openstack.org/cfp/details/87 so I thought I'd implement the blueprint: https://blueprints.launchpad.net/heat/+spec/send-notification I'd like

[openstack-dev] [Heat] Incorporate Auditing Support / Usage Notifications

Hi all There has been some interest in Heat generating usage notifications http://summit.openstack.org/cfp/details/87 so I thought I'd implement the blueprint: https://blueprints.launchpad.net/heat/+spec/send-notification I'd like to ask for suggestions on the content of the notifications. I ha

Re: [openstack-dev] [Heat] HOT Software configuration proposal

On 21/10/13 15:45 -0400, Mike Spreitzer wrote: Steve Baker wrote on 10/15/2013 06:48:53 PM: I've just written some proposals to address Heat's HOT software configuration needs, and I'd like to use this thread to get some feedback: https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-

Re: [openstack-dev] [Heat] Plugin packaging

On 15/10/13 16:05 -0700, Tim Smith wrote: Hi Sam, We wrote a Heat resource plugin as well [1] The trick to getting heat to auto-discover a module is to install it to the /usr/lib/heat (or possibly, but unlikely, /usr/lib64/heat) directory. I have found that the setuptools incantation: sudo py

Re: [openstack-dev] "Thanks for fixing my patch"

On 13/10/13 22:58 +, Jeremy Stanley wrote: On 2013-10-14 09:45:38 +1100 (+1100), Angus Salkeld wrote: Note the commit will "authored" by the original poster, so perhaps if you modify a patch we should add a "Modified-by: " line to indicate that it was dual authored. &

Re: [openstack-dev] "Thanks for fixing my patch"

On 11/10/13 11:34 -0700, Clint Byrum wrote: Recently in the TripleO meeting we identified situations where we need to make it very clear that it is ok to pick up somebody else's patch and finish it. We are broadly distributed, time-zone-wise, and I know other teams working on OpenStack projects h

Re: [openstack-dev] [Heat] HOT Software orchestration proposal for workflows

On 11/10/13 14:25 -0400, Lakshminaraya Renganarayana wrote: Excellent discussion on various issues around orchestration and coordination -- thanks to you all, in particular to Clint, Angus, Stan, Thomas, Joshua, Zane, Steve ... After reading the discussions, I am finding the following themes em

Re: [openstack-dev] [Heat] HOT Software orchestration proposal for workflows

improvements to the HOT format and with some new resource types - IMHO. -Angus On Thu, Oct 10, 2013 at 4:25 AM, Angus Salkeld wrote: On 09/10/13 19:31 +0100, Steven Hardy wrote: On Wed, Oct 09, 2013 at 06:59:22PM +0200, Alex Rudenko wrote: Hi everyone, I've read this thread and I

Re: [openstack-dev] [Heat] HOT Software orchestration proposal for workflows

On 09/10/13 19:31 +0100, Steven Hardy wrote: On Wed, Oct 09, 2013 at 06:59:22PM +0200, Alex Rudenko wrote: Hi everyone, I've read this thread and I'd like to share some thoughts. In my opinion, workflows (which run on VMs) can be integrated with heat templates as follows: 1. workflow defini

Re: [openstack-dev] [Heat] HOT Software orchestration proposal for workflows

On 09/10/13 00:53 +0400, Stan Lagun wrote: Hello, I’m one of the engineer working on Murano project. Recently we started a discussion about Murano and Heat Software orchestration and I want to continue this discussion with more technical details. I hope you are going to be at summit, as I expe

Re: [openstack-dev] [heat] puppet & heat config file

On 27/08/13 19:20 +0100, Steven Hardy wrote: On Mon, Aug 26, 2013 at 02:50:16PM +1000, Ian Wienand wrote: Hi, The current heat puppet modules don't work to create the heat config file [1] My first attempt [2] created separate config files for each heat component. It was pointed out that confi

Re: [openstack-dev] [heat] Propose Liang Chen for heat-core

On 22/08/13 16:57 +0100, Steven Hardy wrote: Hi, I'd like to propose that we add Liang Chen to the heat-core team[1] Liang has been doing some great work recently, consistently providing good review feedback[2][3], and also sending us some nice patches[4][5], implementing several features and f

Re: [openstack-dev] [Heat] How the autoscale API should control scaling in Heat

On 15/08/13 17:50 -0500, Christopher Armstrong wrote: *Introduction and Requirements* So there's kind of a perfect storm happening around autoscaling in Heat right now. It's making it really hard to figure out how I should compose this email. There are a lot of different requirements, a lot of d

Re: [openstack-dev] [Heat] event table is a ticking time bomb

On 13/08/13 10:48 +1200, Steve Baker wrote: On 08/13/2013 10:39 AM, Angus Salkeld wrote: On 12/08/13 16:52 -0400, Doug Hellmann wrote: On Mon, Aug 12, 2013 at 4:11 PM, Clint Byrum wrote: Excerpts from Doug Hellmann's message of 2013-08-12 12:08:58 -0700: > On Fri, Aug 9, 2013 at

Re: [openstack-dev] [Heat] event table is a ticking time bomb

3-08-09 06:16:55 -0700: > > > > > > On 08/08/2013 11:36 PM, Angus Salkeld wrote: > > > > On 08/08/13 13:16 -0700, Clint Byrum wrote: > > > >> Last night while reviewing a feature which would add more events to > > the > > &g

Re: [openstack-dev] [Heat] event table is a ticking time bomb

On 08/08/13 13:16 -0700, Clint Byrum wrote: Last night while reviewing a feature which would add more events to the event table, it dawned on me that the event table really must be removed. https://bugs.launchpad.net/heat/+bug/1209492 tl;dr: users can write an infinite number of rows to the

Re: [openstack-dev] [Heat] The way to use one config file with new oslo module

On 06/08/13 18:09 +0200, Emilien Macchi wrote: Hi, Since https://review.openstack.org/#/c/36476/ has been merged, heat could use only one configuration file : heat.conf instead of heat-engine.conf, heat-api.conf, etc. I would like your thoughts about deleting old configuration files, since that

Re: [openstack-dev] [Ceilometer] Alarming should be outside of Ceilometer as a separate package.

On 02/08/13 13:26 -0300, Sandy Walsh wrote: On 08/02/2013 12:27 PM, Eoghan Glynn wrote: On 08/01/2013 07:22 PM, Doug Hellmann wrote: On Thu, Aug 1, 2013 at 10:31 AM, Sandy Walsh mailto:sandy.wa...@rackspace.com>> wrote: Hey y'all, I've had a little thorn in my claw on this topi

Re: [openstack-dev] [Heat] Unique vs. non-unique stack names

On 31/07/13 14:36 +0200, Zane Bitter wrote: On 30/07/13 21:34, Jason Dunsmore wrote: Hello Heat devs, I've started doing some testing to find multi-engine bugs, and I discovered that it's possible to create two stacks with the same name when only a single heat-engine is running. Here are the r

Re: [openstack-dev] [Ceilometer] Nomination for Mehdi Abaakouk

On 31/07/13 10:56 +0200, Julien Danjou wrote: Hi, I'd like to propose to add Mehdi Abaakouk (sileht) to ceilometer-core. He has been a valuable contributor for the last months, doing a lot of work in the alarming blueprints, and useful code reviews. +1 -- Julien Danjou -- Free Software hack

Re: [openstack-dev] [Heat] Multi region support for Heat

On 26/07/13 09:43 -0700, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2013-07-26 06:37:09 -0700: On 25/07/13 19:07, Bartosz Górski wrote: > We want to start from something simple. At the beginning we are assuming > no dependencies between resources from different region. Our first u

Re: [openstack-dev] [Heat] Multi region support for Heat

On 22/07/13 16:52 +0200, Bartosz Górski wrote: Hi folks, I would like to start a discussion about the blueprint I raised about multi region support. I would like to get feedback from you. If something is not clear or you have questions do not hesitate to ask. Please let me know what you think

Re: [openstack-dev] [Heat] awareness of nova cells, availability zones etc.

On 09/07/13 11:59 -0400, Eoghan Glynn wrote: Hi Folks, Just wondering to what extent Heat deployment policies can be made nova cell/AZ-aware? For example, one could envisage a situation in which it would sense for an autoscaling group to have cell-affinity, but also have AZ- anti-affinity with

Re: [openstack-dev] [Heat] re: discussion about passing metadata into provider stacks as parameters

- Original Message - > From: "Clint Byrum" > To: openstack-dev@lists.openstack.org > Sent: Thursday, 27 June, 2013 3:55:17 AM > Subject: Re: [openstack-dev] [Heat] re: discussion about passing metadata > into provider stacks as parameters > > On 2013-0

Re: [openstack-dev] Termination of the title line of commit messages

On 24/06/13 22:50 +0100, Mark McLoughlin wrote: Hey, Pulling this out of gerrit for discussion. Background is one of my patches to diskimage-builder was -1ed because I terminated the title line of the commit message with a period: https://review.openstack.org/33262 This is actually the exact

Re: [openstack-dev] [Heat] autoscaling question

On 21/06/13 18:56 +0200, Patrick Petit wrote: Dear All, I'd like to have some confirmation about the mechanism that is going to be used to inform Heat's clients about instance create and destroy in an auto-scaling group. I am referring to the wiki page at https://wiki.openstack.org/wiki/Heat/

Re: [openstack-dev] [Heat] re: discussion about passing metadata into provider stacks as parameters

On 20/06/13 22:19 -0400, cbjc...@linux.vnet.ibm.com wrote: So anyway, let's get back to the topic this thread was discussing about - "passing meta data into provider stacks". It seems that we have all reached an agreement that deletepolicy and updatepolicy will be passed as params, and metad

Re: [openstack-dev] [Heat] Does it make sense to have a resource-create API?

On 18/06/13 23:32 +, Adrian Otto wrote: Yes. I think having a POST method in the API makes perfect sense. Assuming we reach agreement on that, the next question that comes up is: Err, I am not convinced. Before that, I think it's worth highlighting the different proposals/requirements he

<    1   2   3