Dredging up this thread because I was reminded of it today by a question
on ask.openstack.org.
On 18/07/14 09:19, Ayenson, Michael D. wrote:
Hello All,
My name is Mika Ayenson and I have to privilege to intern at Johns Hopkins - Applied
Physics Lab. I'm really excited to release the latest p
Amidst all the discussion about layers and tents there has been this
lurking issue about Docs and their need to prioritise work that we
haven't really done a deep dive on yet. I'd like to start that
discussion by summarising my understanding of the situation, and
hopefully Anne and others can j
On 06/10/14 06:07, Thierry Carrez wrote:
Jay Pipes wrote:
On 10/03/2014 09:18 PM, Zane Bitter wrote:
The prospect of a much larger tent with many more projects in
OpenStack-proper shines a spotlight on the scalability of the Docs team,
and in particular how they decide which projects are
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 maintains a very respectable review rate[2] with
help
Greetings OpenStackers,
I would like to announce my candidacy for the OpenStack Technical Committee.
I have worked closely with the TC since around the time that Heat was
incubated, two years ago. I have been a regular participant in TC
meetings throughout the Juno cycle as the Heat PTL, so I a
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, o
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 one
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 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/14 16:30, Clark
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
co
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
OpenStack-dev@lis
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 disabl
On 17/03/14 21:18, Mike Spreitzer wrote:
Zane Bitter 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
(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
https://github.com/istalke
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 OS
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, confu
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
On 19/03/14 17:13, Stan Lagun wrote:
On Wed, Mar 19, 2014 at 9:18 PM, Zane Bitter 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 workflows and ALM
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 nece
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 so
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 editti
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 befor
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 works
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 th
On 03/04/14 08:48, Doug Hellmann wrote:
On Wed, Apr 2, 2014 at 9:55 PM, Zane Bitter 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 itself that can do the
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 a
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. OS::
I was just going to let this thread die, because it's clear that we're
just approaching this from different philosophical viewpoints, and I
think that we need _both_ viewpoints expressed in the community. Trying
to change each other's mind would be as pointless as it is futile ;)
That said, it
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
chang
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 or
at we can
claim is Not Our Fault. I would still prefer to see some sort of
interface that results in the dependencies mentioned above occurring
naturally in the template - the alternative is to heavily document how
to do this yourself using get_attr to get, e.g. the IP address of a
Serve
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 :
The Neutron API is a constant cause of pain for us as Heat developers, but
afaik we've never attempted to bring u
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
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. Adding/Rem
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 ev
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 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
debuggin
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 sh
On 15/04/14 17:59, Mike Spreitzer wrote:
Clint Byrum 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 not installed
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 p
On 16/04/14 05:53, Thomas Spatzier wrote:
IMO, it would be desirable to not have things like yum or apt appear in the
template explicitly. For many packages it seems like at least the top level
package names (not including distro specific versioning strings) are equal
across distros so when speci
A few reminders about design summit sessions for Heat...
* The deadline for proposals is the 20th of April, i.e. the end of this
week. Get your proposals in now.
* The Design Summit isn't the place to introduce feature proposals. The
place to introduce proposals is the mailing list and there'
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 righ
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 at
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 d
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 u
At the beginning of this year we introduced alternating times for the
Heat weekly IRC meeting, in the hope that our contributors in Asia would
be able to join us. The consensus is that this hasn't worked out as well
as we had hoped - even the new time falls at 8am in Beijing, so folks
are regul
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 I
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 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 s
On 25/04/14 08:30, Denis Makogon wrote:
Hello Trove/Heat community.
I'd like to start thread related to required use cases (from Trove
perspective). To support (completely) Heat in Trove, it neeeds to
support required operations like:
1.
Resize operations:
- resize a volume (to bi
On 25/04/14 13:50, Chris Friesen wrote:
On 04/25/2014 11:01 AM, Mike Spreitzer wrote:
Zane Bitter 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 e
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 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 server
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 this
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 dist
On 01/07/14 21:09, Mike Spreitzer wrote:
Zane Bitter 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 hol
On 02/07/14 02:41, Mike Spreitzer wrote:
Zane Bitter 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 abilit
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 vali
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 rele
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
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! :)
a)
Hello Heatists,
I've updated the etherpad with some information about accommodation for
the mid-cycle meetup:
https://etherpad.openstack.org/p/heat-juno-midcycle-meetup
For those signed up, now would be a good time to book if you haven't
already. If you plan to attend but haven't signed up ye
On 08/07/14 17:13, Angus Salkeld wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/07/14 09:14, 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 implementin
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
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
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 the
Heat API
- If
On 10/07/14 05:34, Steven Hardy wrote:
> >The other approach is to set up a new container, owned by the user, every
time. In that case, a provider selecting this implementation would need to make it
clear to customers if they would be billed for a WaitCondition resource. I'd prefer
to avoid th
On 09/07/14 22:38, Mike Spreitzer wrote:
Zane Bitter wrote on 07/01/2014 06:54:58 PM:
> 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 functi
On 11/07/14 09:37, Tomas Sedovic wrote:
Hi all,
This is a follow-up to Clint Byrum's suggestion to add the `Map`
intrinsic function[0], Zane Bitter's response[1] and Randall Burt's
addendum[2].
Sorry for bringing it up again, but I'd love to reach consensus on this.
The summary of the previous
The Technical Committee has been conducting an analysis of existing
projects to ensure they comply with the same criteria to which newly
incubated/graduated projects are being held. Heat is one of the last
projects to undergo this analysis, so it will be happening soon -
possibly as soon as tom
On 14/07/14 12:21, Tomas Sedovic wrote:
On 12/07/14 06:41, Zane Bitter wrote:
On 11/07/14 09:37, Tomas Sedovic wrote:
[snip]
3. List of IP addresses of all controllers:
https://github.com/openstack/tripleo-heat-templates/blob/a7f2a2c928e9c78a18defb68feb40da8c7eb95d6/overcloud-source.yaml
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
I have gone thru the Heat Database and found the drawbacks in the
existing model as listed below. Could you review and add anything
missing here. Thanks.
Heat Database model is having following drawbacks:
1.Duplicate information
2.Incomplete namin
On 17/07/14 07:51, Ryan Brown wrote:
On 07/17/2014 03:33 AM, Steven Hardy wrote:
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
SNIP
*Resource*
Status & action should be enum of predefined status
+1
Rsrc_metadata - make
On 25/07/14 13:50, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-24 12:09:39 -0700:
On 17/07/14 07:51, Ryan Brown wrote:
On 07/17/2014 03:33 AM, Steven Hardy wrote:
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj
On 26/07/14 00:04, Anant Patil wrote:
Hi,
When we do a stack update, I see that there are 2 copies of raw_template
stored in database for each update. For n updates there are "2n + 1"
entries of raw_template in database. Is this expected or is it a bug?
When I dug more into it, I see that the de
On 18/07/14 06:02, Dimitri Mazmanov wrote:
On 18/07/14 11:20, "Steven Hardy" wrote:
On Fri, Jul 18, 2014 at 09:02:33AM +, Dimitri Mazmanov wrote:
Hi,
I¹m working on the following use-case:
I have a stack template containing a custom resource - my_res - that
upon
handle_create invokes cre
On 30/07/14 02:21, Anant Patil wrote:
On 28-Jul-14 22:37, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
On 26/07/14 00:04, Anant Patil wrote:
When the stack is updated, a diff of updated template and current
template can be stored to optimize database. A
This is your reminder that two weeks from now we'll be in the middle of
the Heat mid-cycle meetup in Raleigh, NC. (The meetup runs from August
18-20.)
If you plan to attend, make sure you are signed up on this list by the
end of this week:
https://etherpad.openstack.org/p/heat-juno-midcycle-
On 06/08/14 10:37, Anant Patil wrote:
Hi,
I see that the stack delete method is too long to comprehend easily
without going to-and-fro few times. I think we should refactor it and
move out the "UpdateReplace" related logic for backup stack to another
method. We can also move the user credentials
On 04/08/14 19:18, Yuriy Taraday wrote:
Hello, git-review users!
I'd like to gather feedback on a feature I want to implement that might
turn out useful for you.
I like using Git for development. It allows me to keep track of current
development process, it remembers everything I ever did with
On 06/08/14 18:12, Yuriy Taraday wrote:
2. since hacking takes tremendous amount of time (you're doing a Cool
>>Feature (tm), nothing less) you need to update some code from master, so
>>you're just merging master in to your branch (i.e. using Git as you'd
>>use it normally);
>>
>
>This is not h
On 07/08/14 13:22, Tomas Sedovic wrote:
Hi all,
I have a ResourceGroup which wraps a custom resource defined in another
template:
servers:
type: OS::Heat::ResourceGroup
properties:
count: 10
resource_def:
type: my_custom_server
properti
On 08/08/14 11:07, Tomas Sedovic wrote:
On 08/08/14 00:53, Zane Bitter wrote:
On 07/08/14 13:22, Tomas Sedovic wrote:
Hi all,
I have a ResourceGroup which wraps a custom resource defined in another
template:
servers:
type: OS::Heat::ResourceGroup
properties
On 11/08/14 10:46, Clint Byrum wrote:
Right now we're stuck with an update that just doesn't work. It isn't
just about update-failure-recovery, which is coming along nicely, but
it is also about the lack of signals to control rebuild, poor support
for addressing machines as groups, and unacceptab
On 08/08/14 10:41, Anne Gentle wrote:
- Would have to ensure Rally is what we want "first" as getting to be PTL
since you are first to propose seems to be the model.
I know that at one time it was popular in the trade/gutter press to cast
aspersions on new projects by saying that someone getti
On 11/08/14 14:49, Clint Byrum wrote:
Excerpts from Steven Hardy's message of 2014-08-11 11:40:07 -0700:
On Mon, Aug 11, 2014 at 11:20:50AM -0700, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-08-11 08:16:56 -0700:
On 11/08/14 10:46, Clint Byrum wrote:
Right now we're stuck w
On 11/08/14 15:24, Dan Prince wrote:
Hmmm. We blocked a good bit of changes to get these HOT templates in so
I hate to see us revert them. Also, It isn't clear to me how much work
it would be to fully support the non-HOT to HOT templates upgrade path.
How much work is this? And is that something
On 11/08/14 16:21, Matthew Treinish wrote:
I'm sorry, but the fact that the
docs in the rally tree has a section for user testimonials [4] I feel speaks a
lot about the intent of the project.
What... does that even mean?
"They seem like just the type of guys that would help Keystone with
perf
On 14/08/14 03:21, Malawade, Abhijeet wrote:
Hi all,
I am trying to use heat to create docker containers. I have configured
heat-docker plugin.
I am also able to create stack using heat successfully.
To start container on different host we need to provide 'docker_endpoint' in
template. For th
On 19/08/14 10:37, Jay Pipes wrote:
By graduating an incubated project into the integrated release, the
Technical Committee is blessing the project as "the OpenStack way" to do
some thing. If there are projects that are developed *in the OpenStack
ecosystem* that are actively being developed to
On 11/08/14 05:24, Thierry Carrez wrote:
So the idea that being (and remaining) in the integrated release should
also be judged on technical merit is a slightly different effort. It's
always been a factor in our choices, but like Devananda says, it's more
difficult than just checking a number of
On 02/11/13 05:30, Clint Byrum wrote:
Excerpts from Christopher Armstrong's message of 2013-11-01 11:34:56 -0700:
Vijendar and I are trying to figure out if we need to set the resource_id
of a resource to None when it's being deleted.
This is done in a few resources, but not everywhere. To me i
On 12/11/13 14:59, Alex Heneveld wrote:
One minor suggestion is to consider using a special character (eg $)
rather than reserved keywords. As I understand it the keywords are only
interpreted when they exactly match the value of a key in a map, so it
is already unlikely to be problematic. Howe
On 13/11/13 01:34, Clint Byrum wrote:
Excerpts from Angus Salkeld's message of 2013-11-12 15:22:44 -0800:
>IMO is should just be a template/formatted file.
>
I'd prefer that we have the ability to pull in a chunk of in-line template
as well. Perhaps that is the template resource, I have not tho
101 - 200 of 823 matches
Mail list logo
