Here’s one way:
heat_template_version: 2013-05-23
parameters:
image:
type: string
default: TestVM
flavor:
type: string
default: m1.micro
network:
type: string
default: cirros_net2
resources:
serv_1:
type: OS::Nova::Server
properties:
image: {
Hi,
Interesting thread. I’ve just started looking at Boson myself to manage quotas
across multiple regions. I think one of the cases when having quota management
as a separate service is justified, is a multi-region case [1].
1) Some deployments can share Keystone, so there’s a need to
Hello,
I’m also interested in having OVF package support for applications.
As it was described earlier, there are two main tracks to this – OVF artefacts
in Glance (corresponding driver), and translating OVF descriptors to Heat
templates.
Is there any etherpad from the session?
-
Dimitri
From:
TL;DR Is there any reason why stack-update doesn¹t reuse the existing
parameters when I extend my stack definition with a resource that uses
them?
I have created a stack from the hello_world.yaml template
(https://github.com/openstack/heat-templates/blob/master/hot/hello_world.ya
ml)
It has the
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 creation of another set of resources [r1, r2, r3,
...] (not expressed in the template). These newly created resources are
not associated with the stack. The
On 18/07/14 11:20, Steven Hardy sha...@redhat.com 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 creation of another set
Hi!
Comments inline.
On 20/05/14 21:58, Zane Bitter zbit...@redhat.com wrote:
On 20/05/14 12:17, Jay Pipes wrote:
Hi Zane, sorry for the delayed response. Comments inline.
You are assuming a public cloud provider use case above. As much as I
tend to focus on the utility cloud model, where
Great effort! One question, will this session relate to the overall Heat vision
[1] (Model Interpreters, API Relay, etc)?
-
Dimitri
[1] https://wiki.openstack.org/wiki/Heat/Vision
On 05/05/14 19:21, Thomas Spatzier
thomas.spatz...@de.ibm.commailto:thomas.spatz...@de.ibm.com wrote:
Hi all,
they need (if they
don’t find the right flavor in the global list).
Best Regards,
Solly Ross
- Original Message -
From: Dimitri Mazmanov dimitri.mazma...@ericsson.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, May 5, 2014
clouds may have dynamic resource allocation (impact from under-usage will
be not so big). As transition plan project-scoped flavors may do the job.
On Fri, May 2, 2014 at 5:35 PM, Dimitri Mazmanov
dimitri.mazma...@ericsson.com wrote:
This topic has already been discussed last year and a use
This is good! Is there a blueprint describing this idea? Or any plans
describing it in a blueprint?
Would happily share the work.
Should we mix it with flavors in horizon though? I¹m thinking of having a
separate ³Resources² page,
wherein the user can ³define² resources. I¹m not a UX expert
This topic has already been discussed last year and a use-case was described
(see [1]).
Here's a Heat blueprint for a new OS::Nova::Flavor resource: [2].
Several issues have been brought up after posting my implementation for review
[3], all related to how flavors are defined/implemented in
12 matches
Mail list logo
