I think my reply to Angus covers most of your points, except this one:
On 08/07/14 17:39, Steve Baker wrote:
On 09/07/14 07:08, Zane Bitter wrote:
Constraints, I feel, are very similar to resources in this respect. I
am less concerned about template formats, since there are so few of
them
On 08/07/14 17:17, Steven Hardy wrote:
On Tue, Jul 08, 2014 at 03:08:32PM -0400, Zane Bitter wrote:
I see that the new client plugins are loaded using stevedore, which is great
and IMO absolutely the right tool for that job. Thanks to Angus Steve B
for implementing it.
Now that we have done
On 09/07/14 17:10, Angus Salkeld wrote:
If we could make them separate Python packages within a single Git repo,
I would be +2 on that. I don't know if that's feasible with our current
tooling (though I guess it's not dissimilar to what you're doing with
the contrib stuff in this patch series?).
On 09/07/14 18:33, Randall Burt wrote:
On Jul 9, 2014, at 4:38 PM, Zane Bitter zbit...@redhat.com
wrote:
On 08/07/14 17:17, Steven Hardy wrote:
Regarding forcing deployers to make a one-time decision, I have a question
re cost (money and performance) of the Swift approach vs just hitting
I see that the new client plugins are loaded using stevedore, which is
great and IMO absolutely the right tool for that job. Thanks to Angus
Steve B for implementing it.
Now that we have done that work, I think there are more places we can
take advantage of it too - for example, we currently
On 07/07/14 20:02, Steve Baker wrote:
On 08/07/14 09:25, Zane Bitter wrote:
With the Icehouse release we announced that there would be no further
backwards-incompatible changes to HOT without a revision bump.
However, I notice that we've already made an upward-incompatible
change in Juno
On 08/07/14 08:06, Pavlo Shchelokovskyy wrote:
Hi all,
from what I can tell after inspecting the code, these are the only AWS
resources in master branch (if I haven't missed something) that have
updatable properties that are not supported in AWS:
Many thanks for doing this audit Pavlo! :)
With the Icehouse release we announced that there would be no further
backwards-incompatible changes to HOT without a revision bump. However,
I notice that we've already made an upward-incompatible change in Juno:
https://review.openstack.org/#/c/102718/
So a user will be able to create a
On 07/07/14 18:13, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-07 14:25:50 -0700:
I'd like to propose a policy that we bump the revision of HOT whenever
we make a change from the previous stable version, and that we declare
the new version stable at the end of each
On 01/07/14 21:09, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com wrote on 07/01/2014 07:05:15 PM:
On 01/07/14 16:30, Mike Spreitzer wrote:
Thinking about my favorite use case for lifecycle plug points for cloud
providers (i.e., giving something a chance to make a holistic
On 02/07/14 02:41, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com wrote on 07/01/2014 06:58:47 PM:
On 01/07/14 15:47, Mike Spreitzer wrote:
In AWS, an autoscaling group includes health maintenance functionality
--- both an ability to detect basic forms of failures and an ability
On 01/07/14 16:23, Mike Spreitzer wrote:
An AWS autoscaling group can span multiple availability zones in one
region. What is the thinking about how to get analogous functionality
in OpenStack?
Correct, you specify a list of availability zones (instead of just one),
and AWS distributes
On 01/07/14 15:47, Mike Spreitzer wrote:
In AWS, an autoscaling group includes health maintenance functionality
--- both an ability to detect basic forms of failures and an ability to
react properly to failures detected by itself or by a load balancer.
What is the thinking about how to get
On 01/07/14 16:30, Mike Spreitzer wrote:
Thinking about my favorite use case for lifecycle plug points for cloud
providers (i.e., giving something a chance to make a holistic placement
decision), it occurs to me that one more is needed: a scale-down plug
point. A plugin for this point has a
On 26/06/14 18:08, Steve Baker wrote:
I'd like to nominate Sergey Kraynev for heat-core. His reviews are
valuable and prolific, and his commits have shown a sound understanding
of heat internals.
http://stackalytics.com/report/contribution/heat-group/60
+1
On 23/06/14 19:25, Clint Byrum wrote:
Hello! I would like to turn your attention to this specification draft
that I've written:
https://review.openstack.org/#/c/100012/1/specs/convergence-continuous-observer.rst
Angus has suggested that perhaps Ceilometer is a better place to handle
this. Can
I am pleased to announce that I have booked the facilities required for
the Heat mid-cycle meetup for Juno, as discussed at the Heat IRC meeting
this week.[1] Therefore I can confirm that the meetup will be held:
Monday 18th - Wednesday 20th August
@ Red Hat Tower in Raleigh, North Carolina
On 16/06/14 13:56, Nikhil Manchanda wrote:
Denis Makogon writes:
Because Trove should not do what it does now (cloud service orchestration
is not the part of the OS Database Program). Trove should delegate all
tasks to Cloud Orchestration Service (Heat).
Agreed that Trove should delegate
There has been a lot of interest in holding a Heat meetup during the
Juno cycle. We have the opportunity to piggy-back on the TripleO meetup
- and I expect at least some Heat developers to attend that - but we
also know that some key people from both Heat and TripleO will be unable
to attend
On 05/06/14 03:32, yang zhang wrote:
Thanks so much for your commits.
Date: Wed, 4 Jun 2014 14:39:30 -0400
From: zbit...@redhat.com
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [heat] Resource action API
On 04/06/14 03:01, yang zhang wrote:
Hi all,
Now
On 05/06/14 12:03, Kurt Griffiths wrote:
I just learned that some projects are thinking about having the specs
process be the channel for submitting new feature ideas, rather than
registering blueprints. I must admit, that would be kind of nice because
it would provide some much-needed structure
On 04/06/14 03:01, yang zhang wrote:
Hi all,
Now heat only supports suspending/resuming a whole stack, all the
resources of the stack will be suspended/resumed,
but sometime we just want to suspend or resume only a part of resources
Any reason you wouldn't put that subset of resources into
On 29/05/14 18:42, Tripp, Travis S wrote:
Hello everyone!
At the summit in Atlanta we demonstrated the “Graffiti” project
concepts. We received very positive feedback from members of multiple
dev projects as well as numerous operators. We were specifically asked
multiple times about getting
Last week we agreed[1] to follow that other project in setting up a
specs repo.[2] (Many thanks to Ying, Monty and Clint for getting this up
and running.)
I'm still figuring out myself how this is going to work, but the basic
idea seems to be this:
- All new blueprints should be submitted
On 29/05/14 05:26, Thierry Carrez wrote:
Sean Dague wrote:
I honestly just think we might want to also use it as a time to rethink
our program concept. Because all our programs that include projects that
are part of the integrated release are 1 big source tree, and maybe a
couple of little
On 29/05/14 13:33, Mike Spreitzer wrote:
Devananda van der Veen devananda@gmail.com wrote on 05/29/2014
01:26:12 PM:
Hi Jaromir,
I agree that the midcycle meetup with TripleO and Ironic was very
beneficial last cycle, but this cycle, Ironic is co-locating its
sprint with Nova. Our
On 28/05/14 14:52, Sean Dague wrote:
I would agree this doesn't make sense in Neutron.
I do wonder if it makes sense in the Network program. I'm getting
suspicious of the programs for projects model if every new project
incubating in seems to need a new program. Which isn't really a
reflection
On 23/05/14 06:38, Andreas Jaeger wrote:
On 05/23/2014 12:13 PM, Steven Hardy wrote:
[...]
I'll hold my hand up as one developer who tried to contribute but ran away
screaming due to all the XML-java-ness of the current process.
I don't think markup complexity is a major barrier to
I know people are very interested in an update on this, so here's the
plan such as it is.
I'd like to reassure everyone that we will definitely be keeping our
original meeting time of Wednesdays at 2000 UTC, every second week
(including this week).
I want to try out a new time for the
On 20/05/14 12:17, Jay Pipes wrote:
Hi Zane, sorry for the delayed response. Comments inline.
On 05/06/2014 09:09 PM, Zane Bitter wrote:
On 05/05/14 13:40, Solly Ross wrote:
One thing that I was discussing with @jaypipes and @dansmith over
on IRC was the possibility of breaking flavors down
Hi Mistral folks,
Congrats on getting the 0.0.2 release out. I had a look at Renat's
screencast and the examples, and I wanted to share some feedback based
on my experience with Heat. Y'all will have to judge for yourselves to
what extent this experience is applicable to Mistral. (Assume that
On 06/05/14 16:07, Janczuk, Tomasz wrote:
Could this be accomplished with 3 resource groups instead of one? The
first would create the ports, the second floating IPs, and the last the
VMs? In that case, would there be a way to construct a reference to a
particular instance of, say, a port, when
On 05/05/14 13:40, Solly Ross wrote:
One thing that I was discussing with @jaypipes and @dansmith over
on IRC was the possibility of breaking flavors down into separate
components -- i.e have a disk flavor, a CPU flavor, and a RAM flavor.
This way, you still get the control of the size of your
Since this is the designated off week, I'm going to cancel this week's
IRC meeting. By happy coincidence, that will give us until after Summit
to decide on a new alternate meeting time :)
The next meeting will be on the 7th of May, at the regular time (2000 UTC).
cheers,
Zane.
On 25/04/14 12:23, Chris Friesen wrote:
I'm looking to add support for server groups to heat. I've got working
code, but I thought I'd post the overall design here in case people had
objections.
Basically, what I propose is to add a class NovaServerGroup resource.
Currently it would only
On 25/04/14 13:50, Chris Friesen wrote:
On 04/25/2014 11:01 AM, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com wrote on 04/25/2014 12:36:00 PM:
On 25/04/14 12:23, Chris Friesen wrote:
More important is Zane's following question.
The Server class would be extended
On 25/04/14 16:07, Chris Friesen wrote:
On 04/25/2014 12:00 PM, Zane Bitter wrote:
On 25/04/14 13:50, Chris Friesen wrote:
In the nova boot command we pass the group uuid like this:
--hint group=e4cf5dea-4831-49a1-867d-e263f2579dd0
If we were to make use of the scheduler hints, how would
On 23/04/14 20:45, Robert Collins wrote:
Hi, we've got this summit session planned -
http://summit.openstack.org/cfp/details/428 which is really about
https://etherpad.openstack.org/p/heat-workflow-vs-convergence
We'd love feedback and questions - this is a significant amount of
work, but work
A preliminary schedule is available now at:
http://junodesignsummit.sched.org/type/heat
If anybody has feedback or notices any obvious conflicts (you might have
to wait until Monday for all of the tracks to be scheduled), please let
me know.
cheers,
Zane.
On 17/04/14 18:14, Zane Bitter
On 23/04/14 04:14, Thomas Spatzier wrote:
Hi all,
I just realized during a review that I see a couple of more options, so
this poll seems to be thru already ;-)
Yep, I updated the list yesterday :)
Thank you all for your support! I'm glad to be part of this great team!
Congrats, and keep
I'd like to propose that we add Thomas Spatzier to the heat-core team.
Thomas has been involved in and consistently contributing to the Heat
community for around a year, since the time of the Havana design summit.
His code reviews are of extremely high quality IMO, and he has been
reviewing
Resending with [Heat] in the subject line. My bad.
On 22/04/14 14:21, Zane Bitter wrote:
I'd like to propose that we add Thomas Spatzier to the heat-core team.
Thomas has been involved in and consistently contributing to the Heat
community for around a year, since the time of the Havana design
On 17/04/14 00:34, Renat Akhmerov wrote:
Ooh, I confused the day of meeting :(. My apologies, I’m in a completely
different timezone (for me it’s in the middle of night) so I strongly believed
it was on a different day. I’ll be there next time.
Yeah, it's really unfortunate that it falls
On 16/04/14 10:29, Renat Akhmerov wrote:
Can we include action item “Heat/Mistral collaboration” into the agenda of
tomorrow’s Heat community meeting? I’d like to take a few minutes and discuss
this a little bit. If you think it’s not a suitable time/way to discuss it
please let me know your
On 15/04/14 14:31, Mike Spreitzer wrote:
It appears that in Fedora 19 and 20 the Wordpress examples need to
install different packages than in every other release (see my debugging
in https://review.openstack.org/#/c/87065/). I just got a complaint
from Heat validation that I can't do this:
On 15/04/14 15:57, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com wrote on 04/15/2014 03:29:03 PM:
On 15/04/14 14:31, Mike Spreitzer wrote:
It appears that in Fedora 19 and 20 the Wordpress examples need to
install different packages than in every other release (see my
debugging
On 15/04/14 06:16, Qiming Teng wrote:
3) Can/should we do the VM HA orchestration in Heat?
My perception is that it can be done in Heat, based on my limited
understandig of how Heat works. It may imply some requirements to other
projects (e.g. nova, cinder, neutron ...) as well, though Heat
On 15/04/14 17:59, Mike Spreitzer wrote:
Clint Byrum cl...@fewbar.com wrote on 04/15/2014 05:17:21 PM:
Excerpts from Zane Bitter's message of 2014-04-15 13:32:30 -0700:
FWIW, in the short term I'm not aware of any issue with installing
mariadb in Fedora 17/18, provided that mysql is
On 14/04/14 07:01, Steven Hardy wrote:
Hi Rabi,
On Mon, Apr 14, 2014 at 06:44:44AM -0400, Rabi Mishra wrote:
Hi All,
Recently, I've come across some requirements for external
integrations/resources that can be managed like stack resources
(create,update,delete) from the stack.
1.
On 14/04/14 13:40, Steven Hardy wrote:
It's not clear to me why you'd even expect that $third_party_system knows
how to receive SNS notifications, so you might instead want to fire up a VM
with some client on it which knows how to talk to the service directly and
act as a proxy, with lifecycle
On 07/04/14 21:58, Nachi Ueno wrote:
Hi Zane
Thank you for your very valuable post.
We should convert your suggest to multiple bps.
2014-04-07 17:28 GMT-07:00 Zane Bitter zbit...@redhat.com:
The Neutron API is a constant cause of pain for us as Heat developers, but
afaik we've never attempted
On 09/04/14 19:20, Kevin Benton wrote:
is definitely broken as far as I can tell, because you have to give up
dynamic allocation of IP addresses to use it
What do you mean you have to give up dynamic allocation of IP addresses?
A user is never required to enter an IP address for a port if they
address of a
Server or the peer address of a VPNaaS gateway... but if it's possible
to do this manually it seems like it should also be possible to
automatically retrieve the IP addresses in Heat.
cheers,
Zane.
--
Kevin Benton
On Mon, Apr 7, 2014 at 5:28 PM, Zane Bitter zbit...@redhat.com
On 06/04/14 14:23, Steven Dake wrote:
Hi folks,
There are two problems we should address regarding the growth and change
to the HOT specification.
First our +2/+A process for normal changes doesn't totally make sense
for hot_spec.rst. We generally have some informal bar for controversial
The Neutron API is a constant cause of pain for us as Heat developers,
but afaik we've never attempted to bring up the issues we have found in
a cross-project forum. I've recently been doing some more investigation
and I want to document the exact ways in which the current Neutron API
breaks
On 19/02/14 02:48, Clint Byrum wrote:
Since picking up Heat and trying to think about how to express clusters
of things, I've been troubled by how poorly the CFN language supports
using lists. There has always been the Fn::Select function for
dereferencing arrays and maps, and recently we added
On 04/04/14 13:58, Clint Byrum wrote:
We could keep roughly the same structure: a separate template for each
OpenStack service (compute, block storage, object storage, ironic, nova
baremetal). We would then use Heat environments to treat each of these
templates as a custom resource (e.g.
On 03/04/14 03:21, Thomas Herve wrote:
Speaking of offering options for selection, there is another proposal on
adding conditional creation of resources [3], whose use case to enable
or disable a resource creation (among others). My perception is that
these are all relevant enhancements to the
On 03/04/14 08:48, Doug Hellmann wrote:
On Wed, Apr 2, 2014 at 9:55 PM, Zane Bitter zbit...@redhat.com wrote:
We have an issue in Heat where the sample config generator from Oslo is
currently broken (see bug #1288586). Unfortunately it turns out that there
is no fix to the generator script
On 02/04/14 16:45, Mike Spreitzer wrote:
I would like to suggest that a metadata section be allowed at the top
level of a HOT. Note that while resources in a stack can have metadata,
there is no way to put metadata on a stack itself. What do you think?
I think that if you're going to propose
We have an issue in Heat where the sample config generator from Oslo is
currently broken (see bug #1288586). Unfortunately it turns out that
there is no fix to the generator script itself that can do the Right
Thing for both Heat and Nova.
A brief recap on how the sample config generator
Greetings, fellow Heatists. My name is not Steve and I would like to
announce my candidacy for the position of Orchestration PTL.
Most of you, I hope, already know me. I've been working on Heat
full-time essentially since the project started, and I've been a member
of the core team since
On 26/03/14 14:10, Clint Byrum wrote:
This is an issue that affects all of our git repos. If you are using
oslo.config, you will likely also be using the sample config generator.
However, for some reason we are all checking this generated file in.
This makes no sense, as we humans are not
On 21/03/14 18:58, Stan Lagun wrote:
Zane,
I appreciate your explanations on Heat/HOT. This really makes sense.
I didn't mean to say that MuranoPL is better for Heat. Actually HOT is
good for Heat's mission. I completely acknowledge it.
I've tried to avoid comparison between languages and I'm
I completely agree with Georgy, but you raised some questions about Heat
that I want to answer in the interests of spreading knowledge about how
Heat works. A heavily-snipped response follows...
On 21/03/14 05:11, Stan Lagun wrote:
3. Despite HOT being more secure on the surface it is not
On 19/03/14 17:13, Stan Lagun wrote:
On Wed, Mar 19, 2014 at 9:18 PM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 19/03/14 05:00, Stan Lagun wrote:
Steven,
Agree with your opinion on HOT expansion. I see that inclusion of
imperative
On 19/03/14 05:00, Stan Lagun wrote:
Steven,
Agree with your opinion on HOT expansion. I see that inclusion of
imperative workflows and ALM would require major Heat redesign and
probably would be impossible without loosing compatibility with previous
HOT syntax. It would blur Heat mission,
On 19/03/14 02:07, Chris Friesen wrote:
On 03/18/2014 11:18 AM, Zane Bitter wrote:
On 18/03/14 12:42, Steven Dake wrote:
You should be able to use the HARestarter resource and functionality to
do healthchecking of a vm.
HARestarter is actually pretty problematic, both in a causes major
On 17/03/14 21:18, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com wrote on 03/17/2014 07:03:25 PM:
On 17/03/14 17:03, Ton Ngo wrote:
- How to handle resources with timer, e.g. wait condition:
pause/resume
timer value
Handle it by only allowing pauses before and after
(I added a couple of tags to the subject; hope this doesn't screw up
anyone's threading.)
On 09/03/14 16:26, Joshua Harlow wrote:
I'd be very interested in knowing the resource controls u plan to add.
Memory, CPU...
I'm still trying to figure out where something like
On 18/03/14 08:01, Ruslan Kamaldinov wrote:
Joshua, Clint,
The only platform I'm aware about which fully supports true isolation and which
has been used in production for this purpose is Java VM. I know people who
developed systems for online programming competitions and really smart kids
tried
On 18/03/14 12:42, Steven Dake wrote:
On 03/18/2014 07:54 AM, Qiming Teng wrote:
Hi, Folks,
I have been trying to implement a HACluster resource type in Heat. I
haven't created a BluePrint for this because I am not sure everything
will work as expected.
The basic idea is to extend the
On 17/03/14 17:03, Ton Ngo wrote:
(reposting as new thread)
I would like to revisit with more details an idea that was mentioned in the
last design summit and hopefully get some feedback.
The scenario is troubleshooting a failed template.
Currently we can stop on the point of failure by
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.
- ZB
___
OpenStack-dev mailing list
On 11/03/14 01:05, Keith Bray wrote:
We do run close to Heat master here at
Rackspace, and we'd be happy to set up a non-voting job to notify when a
review would break Heat on our cloud if that would be beneficial. Some of
the breaks we have seen have been things that simply weren't caught in
Thanks Clark for this great write-up. However, I think the solution to
the problem in question is richer commands and better output formatting,
not discarding information.
On 07/03/14 16:30, Clark Boylan wrote:
But running tests in parallel introduces some fun problems. Like where
do you send
Cool, nice work Josh team!
On 10/03/14 17:23, Joshua Harlow wrote:
This means that the engine no longer has to run tasks locally or in
threads (or greenthreads) but can run tasks on remote machines (anything
that can be connected to a MQ via kombu; TBD when this becomes
oslo.messaging).
Does
On 10/03/14 16:04, Clark Boylan wrote:
On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter zbit...@redhat.com wrote:
Thanks Clark for this great write-up. However, I think the solution to the
problem in question is richer commands and better output formatting, not
discarding information.
On 07/03
On 04/03/14 00:04, Georgy Okrokvertskhov wrote:
First of all let me highlight that Murano DSL was much inspired by
TOSCA. We carefully read this standard before our movement to Murano
DSL. TOSCA standard has a lot f of very well designed concepts and ideas
which we reused in Murano. There is
On 03/03/14 12:32, Joe Gordon wrote:
- if you're reserving resources far before you'll need them, it'll be
cheaper
Why? How does this save a provider money?
If an operator has zero information about the level of future demand,
they will have to spend a *lot* of money on excess capacity or
On 25/02/14 05:08, Thierry Carrez wrote:
The second challenge is that we only started to explore the space of
workload lifecycle management, with what looks like slightly overlapping
solutions (Heat, Murano, Solum, and the openstack-compatible PaaS
options out there), and it might be difficult,
On 28/02/14 02:28, Qiming Teng wrote:
The creation a stack is usually a time costly process, considering that
there are cases where software packages need to be installed and
configured.
There are also cases where a stack consists of more than one VM instance
and the dependency between
On 14/02/14 03:21, Qiming Teng wrote:
On Fri, Feb 14, 2014 at 08:24:09AM +0100, Thomas Spatzier wrote:
Thanks, Thomas.
The first link actually provides a nice inventory of all Resources and
their properties, attributes, etc. I didn't look into this because I
was thinking of the word
On 09/02/14 03:09, Robert Collins wrote:
In principle yes.
You need:
- to write a module to orchestrate the nova flavor API.
https://wiki.openstack.org/wiki/Heat/Plugins
- to configure your policy rules in the cloud in question to let the
heat engine user create flavors
Not quite.
On 04/02/14 13:53, Kevin Conway wrote:
On 2/4/14 12:07 PM, victor stinnervictor.stin...@enovance.com wrote:
The purpose of replacing eventlet with asyncio is to get a well defined
control flow, no more surprising task switching at random points.
I disagree with this. Eventlet and gevent
On 04/02/14 20:34, Robert Collins wrote:
On 5 February 2014 13:14, Zane Bitter zbit...@redhat.com wrote:
That's not a great example, because one DB server depends on the other,
forcing them into updating serially anyway.
I have to say that even in general, this whole idea about applying
On 05/02/14 11:39, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-02-04 16:14:09 -0800:
On 03/02/14 17:09, Clint Byrum wrote:
UpdatePolicy in cfn is a single string, and causes very generic rolling
Huh?
On 03/02/14 17:09, Clint Byrum wrote:
Excerpts from Thomas Herve's message of 2014-02-03 12:46:05 -0800:
So, I wrote the original rolling updates spec about a year ago, and the
time has come to get serious about implementation. I went through it and
basically rewrote the entire thing to reflect
On 30/01/14 06:01, Thomas Herve wrote:
Hi all,
While talking to Zane yesterday, he raised an interesting question about
whether or not we want to keep a LaunchConfiguration object for the native
autoscaling resources.
The LaunchConfiguration object basically holds properties to be able to
On 30/01/14 16:54, Clint Byrum wrote:
I'm pretty sure it is useful to model images in Heat.
Consider this scenario:
resources:
build_done_handle:
type: AWS::CloudFormation::WaitConditionHandle
build_done:
type: AWS::CloudFormation::WaitCondition
properties:
handle:
On 30/01/14 12:20, Randall Burt wrote:
On Jan 30, 2014, at 12:09 PM, Clint Byrumcl...@fewbar.com
wrote:
I would hope we would solve that at a deeper level, rather than making
resources for the things we think will need re-use. I think nested stacks
allow this level of re-use already anyway.
I've noticed a few code reviews for new Heat resource types -
particularly Neutron resource types - where folks are struggling to find
the appropriate way to model the underlying API in Heat. This is a
really hard problem, and is often non-obvious even to Heat experts, so
here are a few tips
On 22/01/14 23:19, ZhiQiang Fan wrote:
you can split H306 to several patches since it contains so much files.
optional: It would be really nice if you can fix the unused import
problem (if exist) in the same time, this seems can be checked via IDE
That check is already enabled.
On Wed, Jan
I don't know about other projects, but we in the Heat project are
constantly on the lookout for people who can be converted into core
reviewers. Inevitably part of that process is evaluating whether someone
has developed the depth of knowledge of the code that would allow them
to catch a
On 22/01/14 06:23, Pavlo Shchelokovskyy wrote:
Hi all,
we have an approved blueprint that concerns reducing number of ignored
PEP8 and openstack/hacking style checks for heat
(https://blueprints.launchpad.net/heat/+spec/reduce-flake8-ignored-rules).
I've been already warned that enabling some
On 18/12/13 04:26, 이준원 wrote:
Hi, stackers,
I know only little about Heat, and I can't wholly follow recent
discussions around multi-region support in this mailing list.
Please help me understand the roadmap or plan about hybrid cloud
and bursting in particular.
I'd like to ask the following
On 18/12/13 05:21, Thomas Herve wrote:
At the design summit we had a discussion[1] about redesigning Neutron
resources to avoid the need for hidden dependencies (that is to say,
dependencies which cannot be inferred from the template).
Since then we've got close to fixing one of those
At the design summit we had a discussion[1] about redesigning Neutron
resources to avoid the need for hidden dependencies (that is to say,
dependencies which cannot be inferred from the template).
Since then we've got close to fixing one of those issues[2] (thanks
Bartosz!), but the patch is
On 16/12/13 15:57, Sayaji Patil wrote:
Hi,
I have installed Openstack with heat using packstack. One thing I
noticed
is that the Orchestration Heat option is only available inside a
project view.
Is this by design ?
My use case it to create a project with images, networks,routers and
On 10/12/13 12:46, Richard Lee wrote:
Hey all,
We're working on a blueprint
https://blueprints.launchpad.net/heat/+spec/preview-stack that adds
the ability to preview what a given template+parameters would create in
terms of resources. We think this would provide significant value for
601 - 700 of 779 matches
Mail list logo
